Roles and Permissions Reference
What Read and Write allow on each permission card, which actions need two permissions, and what only a super admin can do.
A role is a set of ticks on permission cards. Each card covers one part of the platform and has two boxes: Read lets someone see it, Write lets them change it. This page says what those ticks do in practice, so you can decide what a new role needs.
To create or edit roles, see Team Members and Roles.
Rules that apply to every role
- Write includes Read. Ticking Write ticks Read too, and Read stays on until you untick Write.
- Read on Repositories, Project and Media is always on. Every role gets these, and you can't untick them.
- A role applies to everyone who holds it. Changes take effect for all of them a few seconds after you save. Nobody is signed out.
The cards themselves come from the platform, so the list you see may include a few that don't appear below. Those aren't used by the web app's screens yet.
What each card controls
| Card | Read lets them | Write lets them |
|---|---|---|
| Repositories | Open a project's repositories and the repositories list | Create repositories; edit, delete and restore them; change unit settings; restore or delete versions; create, edit and delete label classes |
| Media | Open a repository's images and videos, and the labeling screen | Upload; create folders; move, copy, split and delete media and folders; edit metadata; pin images; label and save drafts; invite people to an image |
| Project | Open a project's overview and settings | Rename a project and edit its description, make it the default, delete it, and create new projects |
| Models | Open the Models list, and the Models and API Integration items in the project drawer | Build and train models; run, stop and delete them; cancel training |
| Tasks | Open task lists and task details; see the Issues tab while labeling | Create, edit, assign, complete and delete tasks and review tasks; add, resolve and delete issues |
| Monitors | Open Monitors in the project drawer | Create and change monitors |
| Connectors | Open Connectors in the project drawer | Create and change connectors |
| Batch Predictions | Open Predictions in the project drawer | Create and manage batch predictions |
| Users | See the Members tab and a project's team members; share a repository; pick people when assigning work | Invite people to a repository and manage who it's shared with, from its share dialog |
| Policies | See the workspace's roles | Create and change roles (together with Users, see below) |
| Billing | See the Invoices tab, download invoices, and see the extra-storage controls and the extra-usage section | Change plan; add, remove and set default cards; update the billing address; buy and change extra storage; turn on extra usage and top up the balance |
| Subscription | (Not used on its own) | Pay for a plan, settle a failed payment, cancel the subscription or a scheduled downgrade (together with Billing) |
| Payment Methods | See saved cards at checkout | Add a new card at checkout |
| API Keys | See the API Keys tab and copy key identifiers | Create and delete API keys |
Monitors, connectors and batch predictions exist only in workspaces whose plan includes them. If the plan doesn't, those drawer items read "Upgrade to Averroes AI to unlock" no matter what the role says.
For monitors, connectors and batch predictions the app only checks Read in advance. A role without Write still sees the buttons, and the change is refused when it's saved.
Labeling is Write on Media
There's no separate labeling card. Labels belong to the image, so someone with Write on Media can label. With only Read, the labeling screen opens in view-only mode: they can look at images and labels but can't save changes, and comments are hidden.
Creating or changing the label classes themselves is Write on Repositories, because it affects every image in the repository.
Actions that need two cards
For these, a role needs both before the button works. The tooltip names whichever part is missing.
| Action | Needs |
|---|---|
| Run or cancel Auto Label | Read or Write on Models, and Write on Media |
| Invite someone to collaborate on an image while labeling | Write on Media, and Read on Users |
| Choose people in task, review and share dialogs | Read on Repositories, and Read on Users |
| Create a New Role | Read and Write on Users, and Read and Write on Policies |
| Pay at checkout, Pay Now, Cancel Subscription, Cancel Downgrade Plan | Write on Billing, and Write on Subscription |
Without Read on both Repositories and Users, the people pickers in those dialogs are simply empty rather than greyed out.
What only a super admin can do
Some actions are reserved for workspace super admins, whatever a role's ticks say. The Super Admin role is built in; you can't edit or delete it.
- Invite people to the workspace, with Invite User or the header Invite button.
- Edit or delete members. Only the organization's owner can manage another super admin.
- Cancel pending invitations.
- Open the Roles tab and create, edit or delete roles.
- Add or remove members of a single project from its settings.
- Download a repository. For everyone else the Download item reads "Only administrators can download".
- Open the Action Log.
- See the Upgrade button on usage-limit banners.
Super admins can also change the plan and pay for it even if their role lacks the billing and subscription ticks.
How the app tells you something is blocked
There are two kinds of "no", and they're fixed in different ways.
A missing permission usually greys the control out. Hovering it gives a message such as "Insufficient permissions. Missing permission: Media Write". Where either of two permissions would do, it says so ("Models Read or Models Write"). A workspace super admin can fix this by changing your role.
Some controls are hidden instead of greyed out, or greyed out without a tooltip (a few menu items, the project name fields). If a whole page is off limits, you'll see "You do not have access to this content. Please contact your organization's admin for access." with a Go Back button.
A plan limit looks different. The control still works, but clicking it offers an upgrade, or the item says the feature isn't in your plan. No role change will help there; the workspace needs a different plan. See Plans and Billing.
So: greyed out with a permission message means ask your admin. An upgrade offer means it's about the plan.
Build a role from the job
Start from what the person does and tick only that.
- A labeler: Write on Media, plus Read on Tasks if they get assigned work, or Write on Tasks if they manage it.
- A reviewer: the labeler's ticks with Write on Tasks, plus Read on Models if they should see predictions.
- An engineer: add Write on Models, and Read on Monitors, Connectors and Batch Predictions if they work with them.
- An administrator: add Users and Billing. Give Policies only to people who should decide what everyone else can do.
Be careful with Write on Policies. Someone who can edit roles can widen their own access.
To check a role, ask someone who holds it to try the thing they need. If it's blocked, the tooltip names what to add.