Skip to main content
Each of these uses features on the free plan unless it says otherwise.

Edit this page

Have a setup worth sharing? Add it.

A separate channel for moderation

Send Modlogs to their own channel so bans, kicks and timeouts are not buried under message logs. Moderators can then press Edit Reason on a modlog to add or correct the reason later, and to attach screenshots as evidence. Dashboard: Logging → Channels → Modlogs.

A private channel for deleted files

Set a Files channel that only senior staff can see. Deleted attachments are then posted there as their own log, away from the rest of your message logs. Dashboard: Logging → Channels → Files.

Keep age-restricted content out of your log channel

A deleted or edited message is logged with what it said. Set an Age-restricted log channel, itself age-restricted, and the message logs from your age-restricted channels go there and not to your other log channels. Dashboard: Logging → Channels → Special categories → Age-restricted. See age-restricted channels.

Split busy servers across channels

Discord limits how fast messages can be posted to one channel. In a large server, give Messages and Voice their own channels. The limit applies per channel, so two channels carry twice as much. The dashboard warns you on the Channels tab when a channel is over the limit.

Stop modlog reasons being rewritten later

Set Modlog reasons to Lock after 24 hours. Moderators can still correct a reason on the day, and after that it stays as written. To freeze one modlog straight away, press its Lock button. That lock is permanent. Dashboard: Logging → Other → Modlog reasons. See modlog reasons.

Hear about it when a staff member is banned

On the Automations page, start a rule from the idea Tell a channel when someone with a role is banned. Choose your staff role and a channel only admins can see, and a role to ping if you want one. Quark posts there whenever a member with that role is banned, with who did it and the reason. See automations.

Keep bot commands out of the logs

Add your bot-commands channel, or a whole channel category, to Logging → Ignore Rules. Add common command messages to Exact content so deleting them is not logged.

Quieter voice logs

If you only care about who was in voice, switch off Stream Start, Stream End, Video Start and Video Stop under Logging → Individual Log Config. Joins, leaves and moves that happen close together are already bundled into one log.

An audit trail for Quark itself

Send Quark Events to a channel only admins can see. It records every change to Quark’s settings in your server: log channels, ignore rules, automation rules, tags, API tokens, dashboard access and subscription changes, with who made the change.

Give moderators the log viewer

Moderators often do not have Manage Server. Give their role the Log viewer preset under Settings → Dashboard Access and they can read and search logs on the web without being able to change anything. See sharing access.

Answers to common questions as tags

Create tags for your rules, your appeal process or your FAQ on the dashboard, then post one with /tags send. Add the user option to mention the member you are answering. See tags.

Hear about outages and updates

When you set a log channel, Quark’s confirmation message in that channel has a button to follow Quark’s developer updates. Press it and downtime notices and announcements from the developers are posted in that channel. Quark’s reply includes a Disable button to stop them. You need Manage Server or Manage Channels to use it. You can also choose the channel, move it or switch the updates off under Settings → Status updates on the dashboard.

A colour for each log type

With Quark Pro or Pro Lite, set an Embed Color per log type so the logs you care about stand out, for example red for bans and grey for voice. See customization.