Permissions & role hierarchy
Give PrynBot the access its enabled modules need.
Review the invitation
The Add to Discord link requests permissions for PrynBot’s supported features. Review Discord’s authorisation screen before adding the bot. Enabling or disabling a module does not automatically rewrite its server role permissions.
Role hierarchy matters
Place PrynBot above roles it must assign or manage. Moderation actions also depend on the target’s role and Discord’s hierarchy rules. Avoid self-role panels that grant management or moderation privileges.
Keep support private
Ticket categories and archive channels must be configured so ordinary members cannot view other people’s conversations. Give the configured support team the access it needs and verify that unrelated roles do not inherit visibility.
Dashboard access
Sign in through Discord. PrynBot checks current server-management permissions before offering configuration access. Owning Premium does not give someone permission to administer a server they do not manage.
Troubleshooting access
Check missing permissions, role order, channel overwrites and bot availability. The ModMail /health command can help staff inspect its support setup. Ask the support team if the cause is unclear.