Managing permissions

The website reads your server list straight from Discord, on every page load, with your signed-in account. A server shows up in your dashboard and can be configured if you meet one of these conditions:

• you're the server owner;
• one of your roles has the Administrator permission;
• one of your roles has the Manage Server permission.

• Without those rights, the server's address shows a page not found.
• If the bot isn't on the server, every page shows "Dispatch.IO™ is not on this server" with the Add Dispatch.IO™ to server button; the page updates on its own as soon as the bot joins.
• A role change on Discord is taken into account on the next page load.

Once on a server's dashboard, the left menu shows three groups: My server, Configuration and Administration.

1. My server: ticket handling, members and XP, leaderboards.
2. Configuration: every bot module.
3. Administration: statistics and logs.

There are no finer per-page rights on the website: anyone who can open a server's dashboard can change all of its settings. To limit who configures the bot, limit who has Administrator or Manage Server on Discord.

For each server, the bot can save roles with a type. They have no effect on website access: the bot uses them on Discord.

Details (which commands, which protections) are in Permissions and roles.

Every website account has one or more team roles. Every new account gets the User role on first sign-in; other roles are assigned by the Dispatch.IO team.

When someone has several roles, they get all of their permissions and their rank is the highest one. Rank drives the hierarchy: you can only change the rights of someone with a strictly lower rank.

The website's administration pages are described in Global bot configuration (team only).

On top of their roles, a person can get an exception on a specific permission:

There can only be one exception per person and per permission. To decide, the website applies this order:

Today, exceptions are managed for documentation permissions, in the Permissions tab of the documentation back office (Members and exceptions section). You need PERMISSION_ASSIGNMENT_GRANT to add one, PERMISSION_ASSIGNMENT_REVOKE to remove one, and a rank strictly higher than the person's (otherwise: "You can't change the rights of a member of equal or higher rank."). Every exception added or removed is recorded in the website's Audit Logs.

Roles and permissions are read from the database through the Redis cache shared by the website and the bot. Every change made from the website clears the relevant cache, so it applies immediately:

A change made directly in the database (by the technical team, outside the website) can therefore take up to 5 minutes (roles, exceptions) or 1 hour (per-role permissions) to apply. Blocking a banned account can also take up to 5 minutes. How the cache works is detailed in Redis and database (team only).

The documentation you're reading is public, except the spaces, categories or pages restricted to a permission. Seven permissions run its back office:

• A restricted item ("Readable by") is only visible to people with the chosen permission: DOCUMENTATION_VIEW, DASHBOARD_VIEW_STATS, BOT_MANAGE, SANCTIONS_VIEW or AUDIT_VIEW. The restriction also applies to everything below it.
• A draft is only visible to people with the View permission or an editing permission (Create, Edit, Translate, Publish, Administer).
• The back office's Permissions tab shows the Rights per role (editable for every role except Root and User, with DOCUMENTATION_MANAGE and the assignment permissions) and the Members and exceptions.

The full guide is in Documentation permissions (team only).

• Managing your servers
• Permissions and roles: permissions on the bot side.
• Sign-in and account
• Synchronisation with the bot