Review audit logs and eligible rollbacks

Audit logs show who changed community data, what changed, and when. They are the first place to investigate an unexpected rank, setting, progression, or moderation action.

Review activityCopy link to Review activity

Open Audit Logs in Clan Labs or use /auditlog. Filter or search with the controls the current view provides, then open an entry for its available detail. The default permission to view audits is Member, but community owners can raise it.

An audit entry can identify an actor as a Discord user, an API key name, or the applicable product workflow. API key secrets are never displayed.

Audit history varies by plan. The Clan Labs plan comparison is authoritative for the retention currently offered. Do not assume an older record remains available after the plan’s retention period.

Roll back an eligible actionCopy link to Roll back an eligible action

Rollback is deliberately narrower than “undo anything.” An entry is eligible only when Clan Labs can construct and validate a safe inverse operation. External state, later changes, or the action type can make an older entry ineligible.

1. Open the exact audit entry.
2. Check the actor, target, original change, and current state.
3. Select Rollback only when the control is offered.
4. Review the proposed reversal and any conflicts.
5. Confirm as the Discord server owner.
6. Wait for completion, then verify the target system and the new rollback audit entry.

Use batch rollback only when Clan Labs presents the option for the selected entries. Follow the preview and progress shown in the dashboard; do not assume availability from a plan name alone.

Safety guidanceCopy link to Safety guidance

• Never use rollback as a substitute for checking current state.
• Avoid reversing an early action after a later legitimate action depends on it.
• If Roblox or Discord timed out, inspect external state before retrying.
• Record a manual correction clearly when an entry is not rollback-eligible.
• Give API keys distinct names so their audit activity is attributable.

Configure Discord delivery with Audit-log delivery. If a rollback control is missing, verify Pro access, Discord server ownership, entry eligibility, and the deployment’s available controls.