Skip to main content
This page is about the permissions Quark needs. For the permissions a member needs to run a command, see the command list.

​
The short version

Giving Quark Administrator avoids every problem on this page, and new log types work as soon as they are released. The invite link asks for it by default.
If you do not want to grant Administrator, Quark needs at least:
  1. View Audit Log on its role, server-wide.
  2. View Channel, Manage Webhooks and Embed Links in every log channel.
  3. View Channel in every channel you want logged.
The rest of this page lists what each permission is for, so you can decide what to leave out. To check your server, run /troubleshoot. It reports every permission Quark is missing in each log channel and what that costs you. One permission Quark can use is not in the invite link and only comes with Administrator: Manage Channels. If you remove Administrator, add Manage Channels yourself if you want invite logs, or want Quark to create #quark-logs during setup. The invite link has not always asked for Manage Messages and Manage Roles. A server keeps the permissions it gave Quark when it was added, so if Quark does not have Administrator in your server, grant those two to its role when you need them.

​
In each log channel

Quark needs these in every channel it sends logs to.

​
Server-wide

​
View Audit Log

Discord only tells a bot who did something through the audit log. Without View Audit Log these log types are never sent:
  • Modlogs: Ban, Unban, Kick, Timeout, Timeout Removed
  • Roles: Role Create, Delete and Update, Role Permissions Updated, Role Icon Update
  • Channels: Channel Create, Delete and Update, the three Channel Permissions logs, all webhook logs, Channel Followed, Unfollowed and Followed Channel Updated
  • Server and members: Server Modified, Server Icon Update, Nickname Update, Role Given, Role Taken, Members Pruned, Bot Added
  • Actions: Invite Delete, and the emoji, sticker and event logs
  • Voice: Moved, Disconnected, Voice Channel Status Updated, Stage Started, Ended and Updated
  • Messages: Delete Multiple Messages, Thread Delete, Thread Updated
The log types table marks each of these. Other logs are still sent, but lose detail:
If Quark cannot tell who did something, the ignore rules for who did it cannot apply to that log.

​
Other server-wide permissions

​
In the channels you want logged

Quark needs View Channel in a channel to log the messages in it. To keep a private channel out of your logs, remove View Channel for Quark in that channel, or add the channel to the ignore rules.

​
For commands

Quark’s own permissions for each command. The member running the command needs their own permissions too. See the command list.

​
For automations

Quark’s own permissions for each action an automation rule can take. The person saving the rule needs their own too, and has to keep them for the rule to go on acting. See who a rule acts for. For a timeout, kick, ban, role change or message delete, Quark’s highest role must also be above the highest role of the member, or of the message’s author. The server owner cannot be acted on. If Quark is missing a permission, that step of the rule is skipped. The rule’s row on the dashboard says why, and Quark posts a Rule Action log about it, at most once an hour for each reason. The same happens when the person who last changed the rule has lost theirs.