Set up logging and moderation
- Connect your Discord account to your active workspace membership. Use the connected server and an active Community & Discord subscription, including Everything.
- An OWNER or ADMIN opens Discord > Moderation, configures Action logging and the optional staff log channel, then clicks Save logging.
- In Moderation cases, enable moderation and warnings as needed, set Warning expiry days and click Save moderation. Zero means warnings do not expire automatically.
- Confirm that the acting moderator and the bot have the specific Discord permission required by the command and sufficient role hierarchy. Dashboard access alone does not bypass Discord's execution checks.
- After an action, review its private Discord result, Moderation cases and Persistent action log. A command being visible does not make it member-accessible.
Choose single or bulk moderation
- For one member, use /kick user user:<member> [reason] or /ban user user:<member> [reason] [delete_messages]. Submitting executes directly; there is no second selector or confirmation. Verify the target before submission.
- For multiple members, use /kick bulk [reason] or /ban bulk [reason] [delete_messages]. Select up to ten members, review the selection and explicitly confirm.
- Read each result. Bulk actions can partly succeed; rerun only for targets that still need action after correcting permissions or hierarchy.
Troubleshooting
If an action is denied, check linked workspace staff membership, active product access, enabled moderation, current Discord permissions and role hierarchy. If an initial audit record cannot be stored, no destructive action is performed. Expired bulk selections require a new command. Do not repeat a successful single-target action merely because there was no confirmation step.
Feature and command reference
Community & Discord adds persistent moderation cases and Discord action logs on top of the existing kick, ban, purge, role-history, and recovery features.
Action logging
/setup-logs can enable or disable persistent event logging and configure an optional staff log channel.
Event groups can include:
- member events
- message events
- role events
- channel events
- moderation events
Message content logging is configurable. If message-event logging is enabled, edited or deleted message content can be stored for the action log.
Audit explorer
/audit can show persistent Discord action-log events with optional category and member filters.
Supported categories include:
- Member
- Message
- Role
- Channel
- Moderation
Warnings and moderation cases
/setup-moderation configures the persistent moderation-case system, warning support, and optional warning expiry.
/warn records a warning against a Discord member.
/warnings shows recent warning cases, optionally filtered to one member.
/modlogs shows persistent moderation cases.
Staff activity
The Moderation dashboard can summarize case actions recorded by staff over the recent reporting window.
Single and bulk moderation from Discord
Before using destructive commands, connect your Discord account to an active CollabOS workspace staff membership: OWNER, ADMIN, LEAD or MANAGER. The workspace needs Community & Discord or Everything. Your current Discord permissions and the bot’s permissions are checked again when the action runs. Moderation must be enabled for the workspace.
/kick user user:<member> [reason] Executes one kick directly. /kick bulk [reason] opens the native selector for 1–10 members and requires confirmation. Both you and the bot need Kick Members. Owner, self, bot and hierarchy protections apply; failures are reported privately.
/ban user user:<member> [reason] [delete_messages] Executes one ban directly. /ban bulk [reason] [delete_messages] uses the multi-member selector and confirmation. Both you and the bot need Ban Members; the same safety protections apply.
Recent-message deletion choices remain None, Last hour, Last day and Last 7 days. Deleted messages cannot be restored by CollabOS.
/timeout duration:<value> [reason] Use a friendly duration such as 10m, 1h, 6h, 1d or 7d. Durations range from 1 minute to a maximum of 28 days. Select up to 10 members, review and confirm. Both you and the bot need Moderate Members. Server owners, administrators, yourself and the bot are protected; hierarchy/manageability restrictions apply.
To remove timeouts, run /timeout duration:remove, select the members and confirm. A failed target is reported independently of successful changes.
/roles delete Use the native multi-role selector to choose up to 10 roles. Review the selection and confirm permanent deletion. This cannot be undone. Both you and the bot need Manage Roles, and you must be linked workspace staff with Community & Discord or Everything.
CollabOS never deletes @everyone, bot-managed or integration-managed roles. Roles must be editable and below the bot’s highest role; they must also be below your highest role unless you own the server. Roles are fetched and checked again immediately before deletion. A role deleted elsewhere or made unmanageable after selection fails individually while other valid roles can still be deleted.
Audit trail and confirmations Destructive commands create CollabOS action-log records for attempted actions and their success or safe failure category. Moderation records include the actor, target, reason and timeout duration where applicable. If the initial audit record cannot be stored, the action is not performed. Bulk confirmations and action results stay private; raw Discord errors are not shown. Pending selections expire after ten minutes or a bot restart, so run the command again if needed.
Existing protected moderation
The previous CollabOS moderation workflows remain available:
- safe purge with preview and confirmation
- kick and ban operations
- recent Discord moderation lookup
- recently removed
- role-history recovery
/recently-removed shows recent kicks, bans, and removed roles from the server.
/recover-role-history uses available Discord audit-log history to recover role assignment history where possible.