Two independent controls, and neither covers the other
An assistant reaching your data has to pass both. That is deliberate — one of them answers „may this organisation use this application at all“, the other „may a machine do this particular thing with it“.
The licence
Exactly as for a person: an application your organisation does not hold a licence for is not reachable, whichever door is used.
The permission matrix
One row per application with four independent switches. No row means nothing is granted — not read-only, not defaults — so a newly deployed application is inert until your organisation switches it on.
The assistant uses the same code a person does
Every tool calls the same service the web page calls — so the licence check, the organisation filter and every validation rule are the same code for a machine as for a person. There is no second, unattended copy of those rules to drift out of step.
At a glance
- Tools available
- 34 across five applications
- Default state
- Nothing granted until your organisation grants it
- Switches per application
- Four, independent: read, create, update, delete
- Scope of a token
- Pinned to one organisation, so it can never read another's rows
- Editing the permissions
- Only from the web, by a person — no tool can edit the matrix