What each role can do¶
When someone asks "why can't I see Settings?" or "who may lift this budget?", the answer is on this page. Two tables: the pages each role finds in the menu, and what each role may read, change or approve in every area. Roles add up, so a person with two roles has both columns.
How to read the tables
- Reads and Changes are about the level the role was given on: a group admin reads and changes their teams and the teams under them, not the whole organisation.
- Everyone signed in is a User as well, so each other column lists what that role adds.
- Vidai decides every action. The menu follows the role; a button that isn't yours isn't offered, and anything refused is explained in words.
Pages in the menu, by role¶
| Menu group › Page | Organisation admin | Organisation viewer | Group admin | Finance | Compliance officer Enterprise | User |
|---|---|---|---|---|---|---|
| Daily › Home | Yes | Yes | Yes | Yes | Yes | Yes |
| › Dashboard | Admin, FinOps, Compliance, Impact report | Admin, Impact report | Admin, FinOps, Compliance, Impact report, for their teams | FinOps, Impact report | Compliance, Impact report | — |
| › Request logs | Every call | Every call | Their teams' calls | Every call, for cost | Every call | Their own calls |
| › Keys | Every key | Reads every key; holds none | Their teams' keys | Their own | Their own | Their own |
| › Approvals | Yes | — | Yes | Yes (budget overrides) | Yes (guardrail overrides) | — |
| Policies › Policies | Yes | Yes | Yes | — | Yes | — |
| › Regulations | Yes | Yes | — | — | Yes | — |
| › Guardrails | Yes | Yes | Yes | — | Yes | — |
| › What applies here | Yes | Yes | Yes | — | Yes | — |
| Who › People, Teams, Roles & access | Yes | Yes | Their part | — | Yes | — |
| › Service accounts Enterprise | Yes | Yes | Their teams' | — | Yes | — |
| › Applications & agents | Yes | Yes | Yes | Their own | Yes | Their own |
| › Environments | Yes | Yes | Yes | Yes | Yes | Yes |
| › Risk | Yes | Yes | — | — | Yes | — |
| Models & routing › Providers | Yes | Yes | — | — | Yes | — |
| › Models | Yes | Yes | Yes | Yes | Yes | Yes |
| › Model access, Routing | Yes | Yes | Yes | — | Yes | — |
| Proof › Audit | Whole log | Whole log | Events about their part | — | Whole log | — |
| › Evidence, Retention & legal hold | Yes | Yes | — | — | Yes | — |
| › Incidents Enterprise | Yes | Yes | — | — | Yes | — |
| › Access reviews, Data subject requests | Yes | — | — | — | Yes | — |
| Money › Cost | Whole organisation | Whole organisation | Their teams | Whole organisation | Their own (others' calls without cost) | Their own |
| › Budgets | Every budget | Every budget | Those they may set, and their own | Every budget | Every budget | Those covering their keys |
| › Prices | Yes | Yes | — | Yes | Yes | — |
| System › Status | Yes | Yes | — | — | Yes | — |
| › Settings | Every section | Reads some sections | — | — | Reads some sections | — |
Anyone given one of the three permissions also finds Approvals in their menu. Everyone can open Your account from the account menu, and anyone without Settings sees their edition under Your edition, from Search or jump to….

What each role may read, change or approve¶
| Area | Organisation admin | Organisation viewer | Group admin | Finance | Compliance officer Enterprise | User |
|---|---|---|---|---|---|---|
| People and teams | Changes | Reads | Changes, in their part | — | Reads | — |
| Roles | Gives any role | Reads | Gives roles in their part | — | Reads | Reads their own |
| Keys | Changes any | Reads; holds none | Issues and changes for their teams and agents | Their own | Their own | Their own |
| Applications and agents | Changes any | Reads | Changes, in their part | Their own | Reads | Their own (as owner) |
| Environments | Changes | Reads | Reads | Reads | Reads | Reads |
| Providers and models | Changes | Reads | Reads models | Reads models | Reads | Reads models |
| Model access | Changes | Reads | Narrows their teams' models | — | Reads | Sees what they may call |
| Prices | Changes, connects the rate card | Reads | — | Manual prices, held price changes, price matches | Reads | — |
| Cost | Locks periods, markups, recompute, exports | Reads | Reads their teams' | Locks periods, markups, recompute, exports | Reads their own | Reads their own |
| Budgets | Sets anywhere, themselves included | Reads | Sets on their teams, never on themselves | Sets anywhere, themselves included | Reads | Sees those covering them |
| Policies and guardrails | Changes | Reads | Changes on their teams | — | Changes policies | — |
| Routing | Changes | Reads | Changes on their teams | — | Reads | — |
| Regulations, retention | Changes | Reads | — | — | Changes | — |
| Risk levels | Changes | Reads | — | — | Changes | — |
| Evidence | Verifies, downloads | Reads | — | — | Verifies, downloads | — |
| Incidents Enterprise | Records, changes, deletes | Reads | — | — | Records, changes | — |
| Access reviews, data subject requests | Runs them | — | — | — | Runs them | — |
| Audit log | Reads, exports | Reads | Reads events about their part | — | Reads, exports | Their own activity |
| Settings | Changes | Reads some | — | — | Reads some | — |
| Safety switches (Stop AI traffic, guardrails off) | Uses them | Sees their state | — | — | Sees their state | — |
| Approvals | Decides | — | Decides in their part | Decides budget overrides | Decides guardrail overrides | Follows their own requests |
| Call content (prompts and replies) | Only as a content reader | Only as a content reader | Only as a content reader | Only as a content reader | Only as a content reader | Only as a content reader |
Finance doesn't change people, teams, keys other than their own, agents, providers, the rate card's connection, rate limits or Stop AI traffic, and doesn't export the audit log. A Compliance officer doesn't change other people's keys, models, providers, prices, budgets, routing or access.
Permissions anyone can be given¶
Three permissions sit beside the roles. They're given on the whole organisation, to anyone, and listed under Permissions on a person's Teams & roles tab. Giving or removing one is recorded in the audit log.
| Permission | What it lets you do | Who has it without being given it |
|---|---|---|
| Approve budget overrides | Decide a group admin's request to lift a budget for a while | Organisation admins and Finance |
| Approve guardrail overrides | Decide a group admin's request to lift a guardrail for a while | Compliance officers |
| Manage approved destinations | Add or remove the models any call may reach | Compliance officers. An organisation admin needs it too, and may give it to themselves |
Call content is a role of its own¶
Nobody reads prompts and replies without Content reader: not an organisation admin, not Finance. An organisation admin can give it, on the whole organisation, a team, an agent or an application. Every read, and every refused try, is recorded in the audit log, and Home tells admins when someone may read every call's content, so the role is never forgotten.