Applications
Role configuration
Restrict who can apply, grant roles on accept, remove roles on submit, ping reviewers.
Role Config has 10 multi-select fields. Each one controls a different part of the lifecycle.
Access gates#
Restricted roles
If the user has any of these roles (or all, depending on match mode), they cannot apply.
Required roles
The user must have these roles to apply. Match mode "all" needs every listed role; "any" needs at least one.
Roles given on outcome#
Accepted roles
Granted when staff accepts the submission.
Denied roles
Granted when staff denies the submission. Useful for marking someone as "Reviewed - rejected" so they cannot reapply forever.
Pending roles
Granted while the submission is in review. Removed automatically on accept or deny. Useful for limiting member access until staff get back to them.
Roles removed on outcome#
Remove on accept
Stripped when accepted. Useful for removing a "Pending Review" role.
Remove on deny
Stripped when denied.
Remove on submit
Stripped the moment they submit. Useful for removing an "Eligible to Apply" role to prevent duplicate submissions.
Notifications#
Ping roles
Mentioned in the pending channel when a new submission lands. Common: a @Reviewers role.
Manager roles
Who can click Accept and Deny. Empty means anyone with channel access can decide. Restrict this if you want only specific staff to review.
Bot role hierarchy
Auditer's top role must sit above any role it is supposed to grant or remove. If saving fails with a hierarchy error, drag Auditer's role above the target role in your server's role list.