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.

Group-bind entries include nickname format and priority changes, plus rank-prefix additions, edits, and removals. A prefix-only edit appears even when Discord role assignments stay the same. Saving an unchanged bind does not create another change entry. To investigate a nickname, compare these entries with the current group-bind configuration.

Premium retains audit history for 90 days. Pro retains it for 365 days. Paid records migrated from the previous V2 audit store keep a transitional 365-day window.

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

Rollback is narrower than “undo anything.” A supported entry must be no more than 30 days old, contain the state needed to reverse it, and still match the current community state.

Clan Labs can prepare rollbacks for supported experience or quota-point changes, medal changes, qualification changes, blacklist changes, settings changes, and warning changes. Individual rank changes use a separate rollback with live Roblox checks. An entry cannot be rolled back when it:

• is older than 30 days, has already been rolled back, or came from the legacy V2 audit store;
• represents an unsupported action such as a suspension;
• is a bulk medal change without a recorded member set;
• has a redacted or missing target or is protected by an active data-rights request;
• contains an unsupported or secret-bearing setting, including API keys, legacy Roblox Open Cloud keys, or Creator OAuth connection settings; or
• conflicts with a later change or the resource’s current state.

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 the selected entries offer it. Review the preview and blockers before confirming, then follow the progress shown in the dashboard.

Reverse an individual rank changeCopy link to Reverse an individual rank change

An eligible rank entry can restore the recorded previous Roblox rank when the member's live rank still matches the change being reversed. The member must not be actively suspended, the previous role must still be assignable, and the Roblox connection must be operational. Rank changes are excluded from batch rollback.

If a rollback outcome is uncertain, refresh and inspect the current rank before retrying. Clan Labs checks whether Roblox confirms the previous rank before completing that attempt; a later rank change can prevent it from proceeding.

Application changesCopy link to Application changes

Creating or updating an application writes an audit entry, including changes made through the API. Eligible individual rollback can reverse creation or restore an edit as a new version within the 30-day window. Submitted responses and join requirements are preserved. Later edits can block rollback, and it cannot close or remove a form required for pending joins.

Public audit detail excludes question text, passwords, and answer keys; the private restore snapshot expires after 30 days. Application entries are excluded from batch rollback. Response deletion is audited but cannot be rolled back. Changes to required applications must be reverted through Pending Join settings rather than audit rollback.

Permission synchronization after rollbackCopy link to Permission synchronization after rollback

An eligible permissions rollback can leave Discord command overrides awaiting reconciliation. When Settings → Permissions shows Sync Discord commands, complete the sync and test with a staff account.

For Former Discord server cleanup needs attention, use Reconnect Discord if requested, then Retry cleanup. Inspect the rollback result and current settings before considering another rollback; a cleanup warning is not evidence that the original reversal failed.

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, the entry age and type, and whether a later change created a conflict.