Tutorial Bring your team in safely Step 8 of 12 · Stage 3: Add your people. 0 of 10 steps done Exit tutorial

Give someone a role

Give a person a role everywhere, in one workspace or in one team, or take one away, on the Access Assignments screen.

Why this step

Give a role only where the job happens. A role given in one team applies only there.

Don't have Roles & Permissions? Install it first: Upload and install an add-on.

Today you only need:

Applies to
Roles & Permissions 1.2 and later
Who can do this
Platform owner, Administrator
Permission
feature.rbac.assignment.edit
Where
Roles and Permissions › Access Assignments (Platform Administration)

Before you start

  • You need Edit Assignment (feature.rbac.assignment.edit). If you hold it only in one workspace or team, you can change assignments only there. Out of the box, only super admins have it.
  • To give a role in a workspace or a team, the person must already be an active member of it. Being given a role never adds anyone to a workspace or team. See Create a workspace and Create a team.
  • To give a role in a workspace or one of its teams, switch to that workspace in the header first. While the switcher is on All Workspaces, only Global can be changed.

Steps

  1. Open Roles and Permissions › Access Assignments.

  2. Under Scope, choose where the role should apply:

    • Global: everywhere.
    • The workspace's name: only while the person works in that workspace.
    • A team's name: only while the person works in that team.

    The Scope label also names the workspace you're in, as in and its name.

  3. Search for the person in Search users… and select them.

  4. In Access for and the person's name, check the Scope again. It lists only the places this person belongs to.

  5. In Roles in and the scope's name, add the roles they should have there, or remove the ones they shouldn't. A role that carries a permission you don't hold in this scope is shown but can't be chosen, and the form says Roles that carry permissions you do not hold in this scope are shown but cannot be given.

  6. Select Save changes.

You see Access updated.

What happens next

The change applies from the person's next click. The Effective access panel beside the form shows what they can now do, and where each permission comes from. See See why someone can do something.

Things to know

  • One scope at a time. Saving changes only the roles in the scope you chose. Removing a team role never touches their global roles, and changing their global roles never touches their team roles.

  • Global roles here and on the Users form are the same. The Roles field on the Users form sets global roles. See Edit a user.

  • Removing a role may not remove the access. If another role or scope also gives the same permission, the person keeps it. Check Effective access.

  • Super admins aren't limited by roles. If you open a super admin, the screen says their assignments don't limit what they can do. Super admins are only listed for other super admins.

  • Last save wins. If two people change the same person's roles in the same scope at once, the later save replaces the earlier one. Each save is recorded in the activity log with what changed.

  • You can only give what you hold. You can give a role only if you hold every permission it carries in this scope. If the person already holds a role like that here, it stays when you save, and you can't remove it. Ask a super admin, or someone who holds those permissions, to change it. See You can't give someone a role or permission.

Check it worked

0 of 2 ticked

Tick each one you can see. Ticks stay on this device; they don't stop you moving on.

Check it worked

Something not right? You can't give someone a role or permission

Back
Steps
Mark done