Give someone access
1
Open Dashboard Access
On the dashboard, open your server and go to Settings → Dashboard Access.
2
Choose who
Under Give someone access, pick A role or One person. Search for the role, or type a member’s name or paste their user ID.
3
Choose what they can do
Pick a preset, or pick Custom and tick individual permissions.
4
Press Give access
Access starts immediately.
Presets
A grant that uses a preset picks up new features added to that preset later. A Custom grant stays exactly as you set it.
The individual permissions for a custom grant are: View logs, View log history, Export logs, View configuration, Manage log channels, Manage log settings, Manage tags, Manage server settings, View analytics and Manage automations.
Manage log settings covers the ignore rules, the options under Logging → Other, the settings of each log type, and creating, editing, sharing and choosing log formats. The Moderator, Log configurator and Full access presets include it.
Manage tags also covers sharing tags with a link, tag bundles and adding tags from a link. On the Marketplace, sharing or adding tags and bundles needs Manage tags, formats and ignore rules need Manage log settings, and automations and lists need Manage automations.
Manage automations lets someone create, edit and delete automation rules. Of the presets, only Full access includes it. Moderator and Log configurator can see the rules but not change them. Adding or changing an action button on a log format needs it too, as well as Manage log settings.
Limits
A role counts once, however many members have it.
Rules
- Only people who manage the server in Discord can give, change or revoke access.
- Access never unlocks a paid feature. Log history and export still depend on the server’s plan.
- Access never replaces a Discord permission. To save an automation rule that times out, kicks, bans, deletes messages, changes roles or sends direct messages, the person also needs the matching permission in Discord. See automations. The same goes for an action button on a log format.
- On a server that has such a rule, the same permission is needed for a logging change that lets more be logged, such as removing an ignore rule or switching a log type on. This applies to people who manage the server too. See changes that let more logs reach a rule.
- Managing access, creating API tokens, resetting the server and billing can never be shared.
- The webhooks Quark posts logs through are never shown to someone with shared access, whatever they can see.
- The bell is read-only for someone with shared access, and does not list changes to dashboard access. Only people who manage the server can mark notifications as read.
- If you remove the role from a member in Discord, their access goes within about 30 seconds. If they leave the server, it goes too.
- Every change is recorded as a Dashboard Access Changed log in your Quark Events channel. The log names the preset and each permission that was given.

