Action

How to Update a Collaborator's Role on Discord

Update a member's role permissions and save the change without losing access yourself.

Is this your situation?

You changed a collaborator's role permissions and the change will not save, or it reset on its own. You also want to update a role without locking your own staff out of settings they need.

The short answer

Changes made to a role's permissions must be saved by clicking Save. After saving, the role can be assigned to the collaborator from the Members tab.

Before you start

  • Confirm permissions are per role Permissions can be assigned per role at the server level and the channel level.Verify: Check whether the setting lives under server or channel permissions.
  • Check command overrides Individual command permissions act as overrides to application-wide permissions.Verify: Review command-level overrides before changing a role broadly.
  • Check your own access level Server owners cannot lock themselves out of a command because they can access all commands.Verify: Confirm whether you are the owner or an administrator.
  • Check channel overrides Channel permissions override server permissions.Verify: Check the channel's Permissions tab for conflicting overrides.

How Discord handles this

  • Permissions let users have specific privileges and functions in their server.
  • A role's permission changes must be saved by clicking Save.
  • Administrators cannot lock themselves out of a command because they can access all commands in the server.
  • A member can be denied access to a command by turning off the command for @everyone.

Step by step

  1. Open Server Settings Go to the server you manage and open Server Settings.Confirm: Check the left panel for the Roles section.
  2. Select Roles Go to the Roles list to find the collaborator's role.Confirm: Check the list for the role name you intend to change.
  3. Open the role's Permissions tab The Permissions tab shows the list of server Permissions that can be assigned under that role.Confirm: Check the tab for the full permissions list.
  4. Grant access before denying it The first step to safely restrict a command is to explicitly allow a specific role to use the command.Confirm: Check that the role shows allowed for the command.
  5. Deny @everyone the command The second step to safely restrict a command is to deny @everyone the ability to use the command.Confirm: Check that @everyone shows denied for the command.
  6. Save the change Changes made to a role's permissions must be saved by clicking Save.Confirm: Check for the Save confirmation at the bottom of the screen.
  7. Assign the role to the collaborator After configuring a role's permissions, the role can be assigned to members of the server.Confirm: Check the Members list for the collaborator's updated role.

Common mistakes

  • Denying before granting A user can accidentally lock themselves out of a command due to command permission overrides.Why it happens: The order of granting and denying was not followed.Already happened: See integration role stuck if a role will not delete.
  • Wrong out-of-order sequence Following the correct order of granting then denying prevents a user with the granted role from being locked out.Why it happens: You deny access before confirming your own role still has it granted.
  • Channel override wins Channel permissions override server permissions.Why it happens: You expect the server-wide role setting to apply everywhere and check the channel last.

Roles at a glance

RoleCan lock itself outPermission scopeWhere set
Owner
Cannot lock themselves out because they access all commands.All commands in the server.Not stated by Discord
Administrator
Cannot lock themselves out because they access all commands.All commands in the server.Not stated by Discord
Collaborator role
Can be locked out through command permission overrides.Per role, at server or channel level.Not stated by Discord
@everyone
Can be denied a specific command.Added together with role allows for an individual's server-wide permissions.Not stated by Discord

Keeping track of who has access

After you have updated the collaborator's role, Delvia is where you track who holds which permissions. Keep a record outside Discord so a reset or an override does not go unnoticed.