Flow reference: Server Management

Edit Role

Rename or restyle a role.

Rename or restyle a role.

When and how to use it

Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.

Configuration fields

Role — role


Choose a role from the correct server by ID or a supported variable. For changes, the bot needs Manage Roles and a higher role.

Input: Text.

Default: ``.


New name (optional) — name


The name used by this action. Command names, variable keys and channel names follow different rules; read the block purpose before reusing a name.

Input: Text with variable suggestions.

Default: ``.


Colour (optional) — color


Color in the format shown by the editor, usually six-digit hex such as #5865F2. Color alone does not change permissions.

Input: Color.

Default: ``.


Show separately — hoist


Whether the role is shown separately in the member list. It does not grant moderation permission.

Input: Fixed choice.

Default: ``.

Available choices (preserve the exact value):
`` — No change
true — Yes
false — No


Mentionable — mentionable


Whether ordinary members can mention the role. This changes mention behavior, not the role's permission set.

Input: Fixed choice.

Default: ``.

Available choices (preserve the exact value):
`` — No change
true — Yes
false — No

Outputs and next steps

out: Continue to the next step.

Test and troubleshoot

Check caller permissions, bot permissions, channel overrides and role hierarchy separately. Test delete/ban/permission changes in a dedicated server rather than against production data.

Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).