Reference

Glossary

On this page

The words UrbaHive uses, in alphabetical order, with a short definition and a link to the page that explains each one.

A to C

Term	Meaning
Accountable (A)	The RACI letter of the person who answers for the result of a step. A step has one A at most. See Describe a step.
Activity	The ordinary type of process step, drawn as a rounded rectangle. The palette of the editor calls it Step. See Build a process in the editor.
Additional contacts	People named on an element besides its responsible, such as experts or stakeholders. See Work with lists and windows.
Advancement status	The status of an application (field Project Advancement Status), such as Active or Pending, taken from a typology. See Typologies.
Application	A piece of software in your IT landscape. It belongs to one program and can run on one server. See Register your applications.
Audit log (Logs)	The record of every change in an organization and of every AI assistant call, readable by all members. See Follow changes in the audit log.
Bidirectional flow	A flow whose data goes both ways between two applications. The map draws it as a dashed arrow with two heads. See Describe data flows.
Capability	A stable business ability, such as "Sell to customer", realized by applications and processes. See Business capabilities.
Contact	A person without a login, Internal or External, whom you can name as responsible or in a RACI. Contacts take no seat. See Manage members and contacts.
Coverage matrix	The grid of capabilities against applications that shows what realizes what. See The coverage matrix.
Criticality	How critical a capability is: Critical, High, Medium or Low. Each link between a capability and an application also has a criticality, which tints the coverage matrix. See Business capabilities.
Custom data field	A field an Owner adds to a type of element, such as "Annual cost" on applications. See Add your own fields.

D to F

Term	Meaning
DAT (Technical Application Document)	A reference to the technical documentation of an application: a link, with its versions. It is not a data model. See Architecture documents (DAT).
DAT version	A numbered version of a DAT, with a status and a date. An application points to the exact version it follows. See Architecture documents (DAT).
Decision	A process step drawn as a diamond. It can send the flow up to three ways, each with a condition. See Decisions, branches and loops.
Domain (process domain)	A business area that groups processes, such as Commercial or Finance. A process has one or more domains; one of them is primary. See The process catalog.
Editor (vendor)	The software vendor of an application, such as SAP or Microsoft, taken from a typology. See Typologies.
Editor (role)	The role that can also delete elements and manage typologies and contacts. See Roles and permissions.
Endpoint	The address Claude calls to reach UrbaHive: `https://app.urbahive.com/api/mcp` on the hosted service. See Connect Claude to UrbaHive.
Event	A process step drawn as a pill, for a start or an end. See Build a process in the editor.
Execution mode	How a step runs: Manual, Semi or Auto. It feeds the optimization score. See Describe a step.
Flow	A data exchange from one application to another, with a required flow type. See Describe data flows.
Flow type	The kind of a flow, such as API or FTP, taken from a typology. Its colour colours the arrows of the map. See Typologies.

G to L

Term	Meaning
Gap	A capability with no application linked to it, flagged with ⚠ in the coverage matrix. See The coverage matrix.
Graph mode	The mode of a process that branches: every arrow is written down. See Decisions, branches and loops.
Impact analysis	A graph of everything one step away from an element. See Impact analysis.
Infrastructure	Where servers run: a cloud provider, a data centre, a site. It is a typology. See Servers and infrastructures.
Invitation	An e-mail an Owner sends to bring someone into an organization with a role. It stays open 7 days. See Invite people.
L1 · Value chain	The level of a process that describes a large chain of activity. L2 maps can be grouped under it. See The process catalog.
L2 · Process map	The level of a process described step by step. See The process catalog.
Layer	The family of an element in the impact analysis: Technical, Applicative, Functional, Business or People. See Impact analysis.
Linear mode	The mode of a process that runs in a line: each step is followed by the next. See Decisions, branches and loops.

M to O

Term	Meaning
MCP (Model Context Protocol)	The standard way for an AI assistant such as Claude to use the tools of an application. UrbaHive's AI connector uses it. See What the AI assistant does.
Member (role)	The role that reads everything and also creates and edits elements, without deleting them. See Roles and permissions.
Optimization score	A score from 0 to 100 per process: the higher, the more there is to gain by improving it. See Understand the optimization score.
Organization	The space that holds a company's data and people. The switch window calls it a workspace. See Organizations.
Organization role	A job title, such as Project Manager, shown next to a person. It gives no rights. See Roles and permissions.
Output	A way out of a step toward another step. A decision has up to three, each with a condition. See Decisions, branches and loops.
Owner	The role that can do everything in an organization, including managing people and settings. See Roles and permissions.

P to R

Term	Meaning
Personal access token	A secret key you create to let Claude reach one organization in your name. See Connect Claude to UrbaHive.
Program	A group of applications, such as a business domain or a portfolio. On the map, a frame around its applications. See Group applications into programs.
RACI	Who does what on a step: Responsible, Accountable, Consulted, Informed. See Describe a step.
Read-only / Read & write	Whether a token lets Claude only read, or also create and change data. See Permissions, tokens and safety.
Redundancy	A capability with more than four primary applications, flagged with ⚠ in the coverage matrix as a probable overlap. See The coverage matrix.
Relation type	How an application serves a step or a capability: Primary, Supporting or Data source. See Describe a step.
Responsible	Two meanings. As a RACI letter (R), the person who does the work of a step. As a field (Responsible or Responsible User), the person who owns an element. See Describe a step.

S to Z

Term	Meaning
Seat	A place in an organization, taken by each member and each pending invitation. Contacts take none. See Invite people.
Server	A machine that applications run on. It sits in one infrastructure at most. See Servers and infrastructures.
Step	One unit of a process: an activity, a decision, an event or a sub-process. See Build a process in the editor.
Sub-process	A step that hands the work over to another process. Double-click its card to open that process. See Sub-process steps.
Swimlane	A horizontal band that holds the steps of one person or one organization role. See Readings, swimlanes and PDF export.
Typology	A reference list of your organization, such as flow types, statuses or process domains. See Typologies.
Value added	A label on a step: Value-added, Non value-added or Control. It does not change the score. See Describe a step.
Viewer	The role that reads everything and changes nothing. See Roles and permissions.
Volume / month	How many times a process runs in a month. It feeds the score and the Optimization page. See Create or edit a process.

Questions and answers: short answers to common questions.
How the building blocks fit together: how the elements connect.
Roles and permissions: the full permissions table.