Discord slash commands
Discord slash commands let teams use CollabOS directly inside Discord without opening the dashboard for every action.
Commands are useful when community operators, collab managers, and team leads are already working inside Discord and want quick access to activity, tracker, role, snapshot, and reporting actions.
Command access
Most commands should only work for people connected to the CollabOS workspace. For sensitive actions, CollabOS should check the Discord user ID, match it to a linked CollabOS account, confirm workspace membership, and verify the member role.
Recommended access rules:
- Owner, Admin, Lead, and Manager can use operational commands
- Viewer can be limited to read-only commands
- Regular Discord members should not be able to change CollabOS data
- Bots should not be allowed to run workspace commands
Sensitive role commands should also require Discord-side permission support. The CollabOS bot needs Manage Roles, and the bot role must be above the role it is assigning or removing.
Analytics commands
/community-summary
Shows a quick server analytics summary, including member count, activity, message activity, voice activity where available, and overall community health signals.
/member-stats
Shows activity stats for one Discord member. This can include messages, recent activity, last active time, voice activity where available, roles, and server-tag status.
/top-active
Shows top active members for a selected period. Use this for reward checks, active member reviews, campaign winners, and community health reports.
/inactive
Shows inactive members based on a selected inactivity window. Use this before cleanup, reactivation campaigns, or role review.
/x-links
Shows recent X / Twitter links tracked from Discord messages. This helps teams review shared posts, campaign links, partner links, and community activity around X.
/collabos-stats
Shows message or voice stats as a Discord embed. Use type:messages for message activity and type:voice for voice activity.
/backfill-history
Starts a Discord message history backfill for channels the bot can access. Use this when the bot was just added and the team needs older message activity included in analytics.
Sync and recovery commands
/sync-discord
Syncs Discord members, roles, and channels into CollabOS from Discord. Use this after adding new roles, changing server structure, or reconnecting the bot.
/recover-role-history
Uses Discord audit logs to recover recent role assignment dates where possible. The bot needs View Audit Log permission. Discord audit log history is limited, so this cannot recover unlimited old history.
Role management commands
/assign-role
Assigns one role to one selected Discord user.
Fields can include:
- user: Discord member receiving the role
- role: role to assign
- duration_days: optional temporary role duration
- reason: audit note
/remove-role
Removes one role from one selected Discord user.
Fields can include:
- user: Discord member losing the role
- role: role to remove
- reason: audit note
/bulk-assign
Assigns one role to a list of members.
Supported targeting options can include:
- users: pasted user IDs or mentions
- source_role: everyone who already has another role
- channel: members currently in a voice or stage channel, or recent participants from a text channel
- duration_days: optional temporary role duration
- exclude_bots: whether to skip bots
- reason: audit note
Use /bulk-assign for workflows like VC participation, active channel participants, role-based reward campaigns, holder reward roles, or temporary campaign access.
/bulk-remove
Removes one role from a list of members.
Supported targeting options can include:
- users: pasted user IDs or mentions
- source_role: everyone who already has another role
- channel: members currently in a voice or stage channel, or recent participants from a text channel
- exclude_bots: whether to skip bots
- reason: audit note
Use /bulk-remove for cleanup, expired campaign roles, temporary event access, or correcting role mistakes.
Snapshot commands
/snapshot-channel
Creates a CollabOS snapshot of members who participated in a selected channel during a time window.
Fields can include:
- channel
- from
- to
- name
- min_messages
- exclude_bots
/grant-snapshot-role
Grants a role to every member in a saved CollabOS snapshot.
Fields can include:
- snapshot_id
- role
- duration_days
- reason
Collab Tracker commands
/tracker add
Adds an early project or collab row to Collab Tracker directly from Discord.
Fields can include:
- project
- stage
- manager
- contact
- raffle_link
- total_spots
- gtd_spots
- fcfs_spots
- raffle_spots
- raffle_type
- requirements
- notes
Supported stages can include:
- Target
- Contacted
- Replied
- Negotiating
- Approved
- Rejected
How /tracker add behaves
Target, Contacted, Replied, Negotiating, and Approved create an early tracker row as Draft so the team can keep working it before the raffle exists.
Rejected should not stay Draft because no raffle is expected. Rejected rows should be saved as Rejected or Cancelled depending on the workspace deal status setup.
Alphabot still handles the main raffle row when the raffle goes live.
/winners-sheet
Saves a Google Sheet winners link to an existing Collab Tracker project group.
Use this when a project has multiple raffles and the team wants one combined winners sheet attached to the main project row.
Fields:
- project: select the main project/group from autocomplete
- url: paste the Google Sheet or winners sheet link
- note: optional note
How /winners-sheet behaves
The project autocomplete should show main project or grouped rows, not every individual raffle row. For example, searching GENJI should show a main group such as GENJI x Pulse Anchor ยท 3 raffles.
When saved, CollabOS should update the project winners sheet URL and show it in the Winners Sheet column inside Collab Tracker. If the project already has a winners sheet, the command should update the existing link instead of creating duplicates.
Reminder command
/reminder
Creates a quick Discord reminder from the bot.
Fields can include:
- task
- when
- channel
๐กBest practices
Use Discord commands for fast operational actions, but keep sensitive setup and review workflows inside the dashboard. After using commands from Discord, review Collab Tracker or Discord Management to confirm manager assignment, status, winners sheet links, role results, and snapshots are correct.