Who can change settings
Three tiers of dashboard access — administrators, Bot Master roles, and per-page grants — and how they differ from what a role can do inside Discord.
On this page
Dashboard access and in-Discord permissions are separate. Giving somebody a dashboard tier changes nothing about what they can do in your server; giving somebody Discord permissions does not, by itself, let them open every dashboard page.
The three tiers
| Tier | Who gets it | What they can open |
|---|---|---|
| Administrator | The server owner, and anyone with Discord's Administrator permission | Everything, including the access lists themselves |
| Bot Master role | Roles an admin names on the Settings page | Every page except the ability to widen their own access |
| Page grant | A role or a single member, granted specific pages | Only the pages ticked in that rule |
Only owners and administrators may edit the lists
A Bot Master cannot add Bot Masters, and a page grant cannot grant pages. Any tier being able to widen itself would make the tier meaningless.
Bot Master roles
Other bots call this Manager Roles. A Bot Master role gives full dashboard access to people who are not Discord administrators — a head moderator who should configure the bot but should not be able to delete your channels.
- Set them on General → Settings → Dashboard access.
- It is a dashboard-only grant. Nothing about the role changes inside Discord.
- Roles that already carry Administrator cannot be added — they have full access anyway, so the entry would be noise.
- Servers where a Bot Master role applies appear in that person's server picker with a key icon.
Page grants
The narrow tier. A rule names one role or one member and ticks the pages they may open — for example, giving your events team the Giveaways page and nothing else.
- Grants stack: somebody matching two rules can open the union of both.
- A new rule grants nothing until you tick pages on it, so its page matrix opens straight away when you create it.
- The matrix is a picture of the sidebar — same groups, same icons, same order — with an All/None control per group.
- Access is enforced on the API as well as in the interface. A granted page is the only thing that person's browser can read or write for that server.
Overview and Settings are grantable too
They are not systems, but they are pages, so a grant can include them. Most grants want the Overview; almost none want Settings.
What staff can do inside Discord
That is a separate question, answered per system rather than centrally:
- Moderation has its own staff roles and its own immunity list, on its Setup tab.
- Ticketing routes each panel to the staff roles you name.
- Every command can be restricted to roles, or to a Discord permission, from Command Info or from the owning system's page.
- Anything not restricted follows Discord's own permissions — which is usually what you want for
/rankand never what you want for/ban.
Seeing who changed what
General → Settings → Recent dashboard activity keeps a running feed of dashboard changes for the server, with who made them. Actions Arclo takes inside Discord are covered by Logging instead.
Still stuck? Ask in the support server — somebody there has almost certainly configured this before.