Flow reference: Moderation
Add Role
Give a role to a member.
Give a role to a member.
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
User — user
Choose the target user. {user} may be a command's selected user; {author} is the caller. Use an ID or the variable picker rather than a display name.
Input: Text with variable suggestions.
Default:
{user}.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.
Format example, not a ready value for your server:
@Member.Default:
@Verified.Reason (audit log) — reason
Describe why the action is taken. Use a meaningful audit/support explanation and avoid sensitive personal details.
Input: Text with variable suggestions.
Default: ``.
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).
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).