An admin hands a developer a limited assistant token
Who is involved
| Role | What they do |
|---|---|
| Tenant admin | Creates the token, chooses what it may do and revokes it when the work ends. |
| Developer | Connects an assistant such as Claude Desktop or n8n with the token. |
Step by step
- Tenant admin
Opens Settings, API tokens and creates a token with a name, the actions it may use, a rate limit and an expiry date.
What they see:The secret is shown once, with a how-to panel for connecting an assistant.
- Tenant admin
Copies the secret into the company's password manager and shares it with the developer.
What they see:Only a fingerprint stays in the token list; the secret cannot be shown again.
- Developer
Adds the gateway address and the token to the assistant's connection settings.
What they see:The assistant lists five tools and finds the module actions by searching.
- Developer
Asks the assistant a read-only question about open invoices.
What they see:The answer comes back, limited to what the token owner may see.
- Developer
Asks the assistant to change something.
What they see:The assistant's own approval prompt for the change tool appears, and the call is refused if the token's actions or the owner's permissions do not allow it.
- Tenant admin
Checks last used on the token list and revokes the token when the project ends.
What they see:The token stops working; a session already open can run for about a minute at most.
Who is told what
No message is sent. Every external call is written to the audit trail and an operating log the admin can review.