UrbaHive Guide
FR

AI assistant

Permissions, tokens and safety

On this page

The AI assistant never has more rights than you, and it only works in the organization of its token. This page explains the rules UrbaHive applies to every call, and how to manage and stop your tokens.

One token, one organization

Everything the assistant reads or writes stays in the organization chosen when the token was created. It cannot see or reach your other organizations, even if you belong to them. To work in two organizations, create two tokens.

UrbaHive checks on every call that the token is valid (not expired, not revoked) and that you are still a member of its organization. Your role is read again on every call: if an Owner changes it, the assistant follows at once.

Two conditions to change anything

To create or change data, both conditions must be met:

  1. the token allows writing (Allow write access was on when you created it);
  2. your role in the organization allows that kind of change.
What the assistant doesOwnerEditorMemberViewer
Read anything in the organizationYesYesYesYes
Create and change elements: applications, flows, servers, programs, processes, steps, capabilities, architecture documents, their links and the people named on themYesYesYesNo
Create and change typologies (flow types, statuses, process domains, editors, infrastructures, organization roles) and contactsYesYesNoNo
Create, change and delete custom field definitionsYesNoNoNo

The note at the bottom of the Connectors tab sums these rules up in one sentence; this table is the complete rule.

When a call is refused, Claude receives a plain message and can tell you why, for example "This token is read-only. A token with write access is required for this tool." or "Your role does not allow creating or modifying data. An Owner, Editor or Member role is required (Viewers are read-only)."

How Claude reaches your map Claude calls the UrbaHive MCP endpoint over HTTPS with your token. UrbaHive checks the token, your membership and the rate limit, and for a change both the token’s write access and your role. It then works only on the token’s organization and records every call in Logs. HTTPS Authorization: Bearer <token> refused: Claude gets a message saying why Claude Claude Desktop claude.ai Claude Code your token UrbaHive MCP endpoint …/api/mcp Checks on every call 1 Token valid: not expired, not revoked 2 You are still a member of its organization 3 At most 60 requests a minute per token 4 A change needs both: the token allows writing and your role allows it Owner, Editor, Member: elements · Owner, Editor: typologies Owner: custom fields · Viewer: read only Your organization’s data only the token’s organization read create update no deletion of elements, except custom field definitions (Owner, after confirmation) Logs one row per tool call Object: mcp_tool_call

The checks every call goes through, and where a refusal goes.

No deletions

The assistant cannot delete data: no application, flow, process or any other element. The only exception is a custom field definition, for an Owner. Even then, the first call only returns a preview; Claude must show it to you and send a second call after you confirm.

Limits

A token can make at most 60 requests per minute. Beyond that, Claude receives "Rate limit exceeded" and must wait a little before trying again.

Everything is recorded

Each call is a row in the organization's Logs, with your name, the tool used and its status. Every member of the organization can see these rows. The token itself is never recorded. See AI assistant calls.

Manage your tokens

The Connectors tab of your personal settings lists your tokens. You see only your own: nobody else, not even an Owner, sees or manages them. Each row shows:

  • its name and status: Active, Expired or Revoked;
  • its organization, and Read & write or Read-only;
  • its first characters, to tell tokens apart;
  • when it was created, when it expires and when it was last used.

Two buttons stop a token:

  • Revoke asks "Revoke token?". Any Claude client using it loses access immediately. The row stays in the list, for the record.
  • Delete token (the trash can) asks "Delete token permanently?" and removes the row entirely.

A token also stops working when it reaches its expiry date, and when you leave the organization or are removed from it.

Warning

If a token may have been seen by someone else, revoke it now and create a new one. Revoking takes effect at once.

Good habits

  • Create read-only tokens, unless you really need Claude to change data.
  • Create one token per device or application, with a name that says which: you can then stop one without the others.
  • Choose a short expiry. You can always create a new token.
  • Revoke a token you no longer use.
  • Read what Claude proposes to change before you confirm, and check the result in UrbaHive or in Logs.