A Role is a named bundle of permissions you assign to one or more users, rather than setting access person-by-person. This guide covers creating a role, understanding the two levels of granularity available for each resource type, and reading a role's access at a glance.
Before you begin#
- Access to Auth → Roles.
- A sense of which resource types (positions, connections, workflows, and so on) the role actually needs to touch, and at what level.
Create a role#
- Open Auth → Roles and select Create Role.
- Enter a Name and an optional Description.
- Save.
A new role starts with zero permissions: nothing is granted until you add it.
Set access for a resource type#
Select a resource type in the role's permissions page, such as Position.
Give access to all resources#
Use All Positions to grant access to every position, including positions created later.
Choose an access level: No access, Read, Update, or Delete. Where available, separate toggles let the role create new resources or execute them. Execute permission requires at least Read access.
Give access to specific resources#
Use Specific Positions to grant access to selected positions only. Find the position in the table and choose Read or Update.
For Workflows and Cuelists, you can also enable Execute for individual items. Specific permissions do not offer Delete.
Combine general and specific access#
Specific permissions can add access, but cannot reduce access granted through All.
For example, set All Positions to Read, then give Update access to one position. The role can view every position but edit only that one.
To give access only to selected positions, leave All Positions at No access and configure the individual rows.
Read a role's access at a glance#
The Roles list shows each role's granted resource types as icon badges. Hovering a badge summarizes what it actually grants: for example, "Full access to all {resource}s" for complete access, or a narrower summary like "Can read and update some {resource}s" when access is partial or scoped to specific items rather than the whole category.
If you get stuck#
What you see | What to try |
|---|
A new role doesn't let its users do anything yet. | That's expected: a new role starts with zero permissions. Add the specific resource-type grants it needs. |
You're not sure whether a role affects future resources too. | Check whether its permission is set on the All {Resource}s card (applies to new resources automatically) or Specific {Resource}s (scoped to what's explicitly listed, not automatic for new ones). |
A user with a role still can't perform an action. | Confirm the role grants at least the right access level (Read/Update/Delete) for that resource type, and, if scoped to specific resources, that the resource in question is actually included. |
You want a quick summary of what a role can do. | Hover its resource-type badges on the Roles list rather than opening each permission individually. |
Where to go next#
