UrbaHive Guide
FR

Work together

Roles and permissions

On this page

Each member of an organization has one role there: Owner, Editor, Member or Viewer. The role decides what the person can change in that organization. You can be Owner in one organization and Viewer in another. The same rules apply in the app and through the AI assistant.

Four roles

Each role can do everything the role below it can, and more:

  • Viewer reads everything: the dashboard, the map, every list, the processes, the alignment pages, the members and the Logs.
  • Member also creates and edits elements: programs, applications, servers, flows, architecture documents, processes and their steps, capabilities, and the links between them.
  • Editor also deletes elements, manages typologies (including organization roles and process domains) and manages contacts.
  • Owner also manages people (invitations, roles, removals), the organization's name and logo, custom fields, export and, on the hosted service, the plan and the deletion of the organization.
What each role can do A Viewer reads everything. A Member also creates and edits elements. An Editor also deletes elements and manages typologies and contacts. An Owner also manages people, the organization’s settings, custom fields, export and the plan. Organization roles such as Project Manager are job titles, not permissions. Contacts have no login and no role. Viewer Reads every workspace page Sees typologies, members, contacts and Logs AI assistant: read only Member + Creates and edits programs, applications, servers, flows, documents, processes, steps, capabilities and their links and everything a Viewer can do Editor + Deletes elements + Manages typologies, including organization roles + Manages contacts and everything a Member can do Owner + Invites people, changes roles, removes members + Organization name and logo + Custom Data Fields, Import/Export + Plan and deleting the organization (hosted) and everything an Editor can do Everyone: Personal Settings, their own AI tokens, leaving the organization (except its only Owner).

Each step of the ladder adds rights to the one below it.

The full table

ActionOwnerEditorMemberViewer
See every workspace page: dashboard, map, lists, processes, alignmentYesYesYesYes
Create and edit programs, applications, servers, flows, architecture documents (DAT) and their versions, processes, capabilitiesYesYesYesNo
Edit process steps, RACI and links (step and application, capability and application, process and process), additional contactsYesYesYesNo
Delete programs, applications, servers, flows, processes, capabilities, DAT references and versionsYesYesNoNo
See the typologiesYesYesYesYes
Create, edit and delete typologies (organization roles, statuses, editors, flow types, infrastructures, process domains)YesYesNoNo
See members and contactsYesYesYesYes
Add, edit and delete contactsYesYesNoNo
Invite people, see and delete invitationsYesNoNoNo
Change a member's role or organization role, remove a memberYes, except their own roleNoNoNo
Leave the organizationYes, if another Owner existsYesYesYes
See the Configuration page (name, logo)YesYes, read onlyYes, read onlyYes, read only
Change the organization's name and logoYesNoNoNo
Define custom fields (Custom Data Fields)YesNoNoNo
Export the organization's data (Import/Export)YesNoNoNo
See and change the plan (hosted service)YesNoNoNo
Delete the organization (hosted service)YesNoNoNo
Read the LogsYesYesYesYes
Personal settings, own AI tokens, delete own accountYesYesYesYes
AI assistant: readYesYesYesYes
AI assistant: create and change elements (token with write access)YesYesYesNo
AI assistant: create and change typologies and contacts (token with write access)YesYesNoNo
AI assistant: custom field definitions (token with write access)YesNoNoNo

A Member can create and edit an element but not delete it. A Member can still remove the parts of an element, such as a step, a RACI letter or a link, because editing them means replacing them.

Organization roles are not permissions

Project Manager, Developer, Business Analyst and the like are organization roles: job titles that describe what a person does. They come from Typologies › Organization Roles. They show next to people in lists, in the RACI pickers and in swimlanes by role. They give no rights: a Project Manager can be a Viewer.

Change the role of a member

Only Owners can change roles.

  1. Open Users & contacts.
  2. On the member's row, click the pencil (Edit user). The "Edit User" window opens.
  3. Choose the Role: Owner, Editor, Member or Viewer.
  4. Optionally, choose an Organization Role, or None.
  5. Click Update. The app says "User updated successfully".
The Edit User window for Jane Smith with her role Editor and her organization role Project Manager.

In the example, Jane Smith is an Editor whose organization role is Project Manager.

  1. Role
  2. Organization role (optional)
  3. Update

An Owner cannot change their own role: "You cannot modify your own role as an owner, but you can modify your organization-specific role." An organization can have several Owners. To hand over ownership, make someone else Owner; they can then change your role.

When your role does not allow something

  • Buttons you cannot use stay visible but greyed out. Hover one to read "You do not have permission to perform this action".
  • Owner-only entries, Custom Data Fields, Plan and Import/Export, are hidden from the sidebar. The Invitations tab and the Invite button are hidden too.
  • If you open an Owner-only page from a link, it shows "Access Denied".

If you need more rights, ask an Owner of the organization.

The AI assistant follows your role

Claude, connected through your token, never has more rights than you, and only in the organization of that token. See Permissions, tokens and safety.