In this section · 4 articles

Grant a permission directly

Give one person a single permission without a role, everywhere, in one workspace or in one team. Use it for exceptions.

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

Before you start

  • You need Grant Permissions Directly (feature.rbac.assignment.grant) as well as Edit Assignment. It isn't in the Administrator role, and nobody gets it automatically: a super admin has to give it on purpose. Without it, the Additional Permissions field isn't shown, and saving roles leaves the person's direct permissions as they are.
  • Think about a role first. If several people need the same combination, create a role or change one instead. Direct permissions are hard to keep track of across many people.

Steps

  1. Open Roles and Permissions › Access Assignments.

  2. Choose the Scope, then search for the person and select them. See Give someone a role for how scopes work.

  3. In Additional Permissions, add the permissions the person needs in that scope. You can search by key, for example feature.core.user.impersonate.

    Permissions you don't hold in this scope yourself are shown but can't be chosen. The field says Permissions you do not hold in this scope are shown but cannot be granted.

  4. To take a direct permission away, remove it from the field.

  5. Select Save changes.

You see Access updated.

What happens next

In Effective access, the permission shows Direct grant under Granted by, with the scope it was given in.

If the person already had a direct permission that you don't hold yourself, it's kept when you save. You can't take away what you couldn't give.