Access & permissions
Access to Clarify is deliberately narrow: only the right people can open your dashboard, and even then they only see what belongs to your server. This page explains how sign-in works, the admin levels your team can hold, and why removing someone takes effect straight away.
For the Discord-side roles that decide who counts as staff on a ticket, see Roles & permissions.
Signing in to the dashboard
You sign in to the Clarify dashboard with Discord — there's no separate password to create or remember. Clarify only ever sees the Discord profile details you authorise (your id, username and email); it never sees your Discord password.
Once you're signed in:
- Your session is kept in a secure, HttpOnly cookie. That means the session can't be read by scripts running in the page — it's handled by the browser and sent only to Clarify.
- The session uses a sliding expiry: it stays valid while you're active and lapses after a period of inactivity, so an unattended tab doesn't stay open forever.
- Every action that changes something (saving settings, connecting an integration, closing a ticket) is CSRF-protected, so another site can't trick your browser into making changes on your behalf.
Admin levels
What a person can do in the dashboard depends on their admin level for that server. There are three:
| Level | Who it's for | What they can do |
|---|---|---|
| Member | Everyone else | No dashboard admin. They can still open and use their own tickets. |
| Helper | Support staff | Can assist with tickets and day-to-day support work. |
| Root | Server owners / super-admins | Full access, including settings, integrations and any ticket on the server. |
Access is checked on every request
Your admin list isn't cached and trusted for the rest of a session — Clarify re-checks it on every request. The practical upshot:
- Add someone as Helper or Root and their access is live immediately.
- Remove someone and their access is revoked instantly, even if they still have a dashboard tab open. Their next action simply won't go through.
Everything is scoped per server
Clarify treats each Discord server as its own island. There is no shared or cross-server view.
- A member can only fetch their own tickets — never anyone else's, and never tickets from another server.
- A Root admin can see any ticket, but only on the servers they administer.
- Settings, integrations, connected payment accounts and stored data all belong to a single server. Connecting Stripe or a data connector for one server never exposes it to another.
So even if the same person helps out on two different servers, each server's dashboard shows only that server's tickets and settings.
How Clarify talks to itself
The Discord bot and the Clarify dashboard/API are separate parts of the product, and they only trust each other through a private, signed channel that customers never touch or configure. You don't set anything up for this — it's mentioned only so you know the bot can't be impersonated to pull your data.
Frequently asked questions
Remove them from your admin list. Because access is re-checked on every request, their dashboard access stops immediately — there's nothing else to do.
Helpers assist with support work, but ordinary members only ever see their own tickets. Full visibility of every ticket on the server is a Root capability.
No. Discord handles the login and only shares the profile details you authorise (id, username, email). Clarify never sees your Discord password.
No. Every ticket, setting and connected account is scoped to a single server. There's no cross-server access.
Related
The relay & your privacy
Who sees what when Clarify relays a ticket — staff stay anonymous in the forum, personal DMs stay private, and members see who helped.
Data & retention
What Clarify stores, what leaves Discord, and how long transcripts are kept — plus how to delete a server or reset your setup.