Recipe
Role responsibilities mapper
Map every Discord role to a concrete set of permissions, channel access rules, and escalation paths so your server scales without permission drift.
Ingredients
- A list of every role currently on your server
- Channel category map (public, staff, admin, logs)
- Escalation policy document (or draft)
Steps
- Audit existing roles. Export your role list. Flag any role that has Administrator or un-scoped Manage Server.
- Define permission tiers. Group roles into Viewer, Member, Moderator, Admin, Owner. Assign baseline permissions per tier.
- Map channel overrides. For each category, document which tiers can read, send, attach, and manage messages.
- Wire escalation paths. Specify which role pings which role for reports, appeals, and emergency lock-downs.
- Validate with a dry run. Create a test account with each tier and walk through every channel to confirm access matches the map.
Outcome
A single source-of-truth spreadsheet or Notion page that every moderator can reference. New roles are added by copying the closest tier template, eliminating guesswork.
Pro tip
Re-audit your role map every 90 days. Servers evolve — permissions that made sense at 200 members often break at 2,000.