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.
Below administrators, Discord's own limits still apply
A Bot Master or a page grant can't set Arclo up to do what they couldn't do by hand: hand out roles above their own, ping @everyone without Mention Everyone, or ban, kick and time out without those permissions. Loading a backup and ban syncs stay with administrators, and deciding form submissions needs a form manager role.
Bot Master roles
Other bots call this Manager Roles. A Bot Master role gives full dashboard access to people who are not Discord administrators. For example, a head moderator who should configure the bot but should not be able to delete your channels.
- Set them on General → Settings → Dashboard access, under Bot Master roles.
- 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. The card lists them separately, under Administrator roles.
- Servers where a Bot Master role applies appear in that person's server picker with a key icon.
Page grants
The narrow tier, under Page access on the same card. Press Give a role or member access, choose A role or One member, then tick 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. A role or member can have only one rule; edit that one instead of adding a second.
- The matrix is a picture of the sidebar (same groups, same icons, same order) with an All/None control per group.
- Pages a rule does not cover are hidden from that person's sidebar, not just locked.
- 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 General tab.
- Ticketing routes each panel to the support team roles you name.
- Every command can be restricted to roles, channels or Discord permissions from Command Info or from the owning system's page. Administrators always pass.
- Anything you leave unrestricted keeps its default: a member command such as
/rankis open to everyone, and a staff command such as/banstill needs the matching Discord permission (or, for moderation, one of Moderation's staff roles).
Seeing who changed what
General → Settings → Recent dashboard activity keeps a running feed of dashboard changes for the server, with who made them. With Logging's Dashboard change log type on, each change is also posted to your log channel. Actions Arclo takes inside Discord are covered by Logging too.
Still stuck? Ask in the support server: somebody there has almost certainly configured this before.