Exclude users from message tracking
Scenario: you want to track messages, edits, and deletions in your server, but make exceptions (don’t track) for your staff team or some selected users. See Channel Management for how rules work.
Solution A: disable tracking per user
Section titled “Solution A: disable tracking per user”To disable every type of tracking (stored messages, edits, deletions), make a rule that disables Message Created tracking — edits and deletions then go untracked for the same context too.
- In the Message Created section, add a new rule.
- Set What should the rule target? to User.
- For Target Discord User, search by username or ID and select them.
- Under Tracking, leave the Inherit toggle unchecked.
- Turn Tracking Enabled off.
This must be repeated for each user, but you can speed it up by duplicating the rule and just changing the targeted user.

Solution B: disable tracking for a role
Section titled “Solution B: disable tracking for a role”If the users you want to exclude share a role, disable tracking for that role instead. If they don’t share one, you can invert this: disable tracking for a role and assign that role to the users you don’t want tracked.
- In the Message Created section, add a new rule.
- Set What should the rule target? to Role.
- For Target Server Role, search by name or ID.
- Under Tracking, leave the Inherit toggle unchecked.
- Turn Tracking Enabled off.
Beware of conflicting rules
Section titled “Beware of conflicting rules”Suppose User A has the roles “Member”, “Incognito Gang”, and “Debate Access”. You already have a rule targeting “Debate Access” that explicitly enables tracking, and now you want to disable tracking for “Incognito Gang”. User A has both — so which rule wins?
Conflict solution A: first match
Section titled “Conflict solution A: first match”If two siblings have the exact same specificity, the first rule wins. So you may want to reorder the rules so the one you want takes precedence.
Conflict solution B: leverage specificity
Section titled “Conflict solution B: leverage specificity”A cleaner fix is to make the “winning” rule the most specific. For example, say “Debate Access” unlocks a “Serious Debates” category and you do want messages there tracked. Create a parent rule targeting the Serious Debates category, and inside it a rule targeting the Debate Access role.
Targeting only the category isn’t enough, because a role is more specific than a channel — so the “Incognito Gang” role rule would still win. You need the more specific category-plus-role setup for the tracking rule to take precedence.