I restricted the bot in Server Settings → Integrations and now staff commands don't work
Open Server Settings → Integrations → ModMailBot and you land on the Command Permissions screen. It has three layers: Roles & Members, Channels, and a Commands list with per-command overrides. The layers combine. A command runs only when every layer allows it. They are AND, not OR.
Restricting Roles & Members works the way you expect. Denying @everyone and allowing your staff roles is a reasonable extra fence.
The Channels row is the trap. Ticket channels are created on demand, one per ticket, so no channel selection made in advance can ever include them. The moment All Channels is denied, staff commands such as /close, /forceclose, and /archive stop working precisely where your staff need them: inside the ticket.
Our recommendation: leave Channels set to All Channels. Restrict by role for a blanket allow or deny, and add per-command overrides if you want an additional safety net. ModMailBot already enforces staff tiers server-side. We encourage layered security; this particular layer only breaks the workflow.
After changing integration permissions, run /diagnose. It detects a denied All Channels row and warns you before your staff run into it.
Why does the bot show Administrator? We never granted that
Every role you attach to the bot contributes permissions. The usual culprit is a shared bot-organizer role that positions bots on the member sidebar and happens to carry Administrator. ModMailBot never requests Administrator and does not need it.
Our recommendation: remove Administrator from that role, or give the bot a dedicated, permission-free role for sidebar placement. Run /diagnose and it names any role granting the bot Administrator, so there is no guessing.
Is there downtime for updates?
No. Updates roll out on our side and apply instantly. Your panels, open tickets, and configuration keep working, and there is nothing to reinstall.
What happens if I kick the bot?
Your ticket channels and archived transcripts stay in your server; they were always yours. The bot's stored configuration and metadata are deleted after a 30 day grace period, so an accidental removal does not destroy your setup. If you want the data gone immediately, an admin can run /data delete before removing the bot.
Still stuck?
The user guide covers setup, staff tiers, intake forms, and archiving in detail. For anything else, join the support server or email support@modmailbot.com.