Skip to content
Clan LabsDocs
API referenceWebsite Open dashboard
Get startedDashboardDiscord botRoblox & Open CloudTroubleshooting
Documentation
Overview
  • Introduction
  • What is Clan Labs?
  • Core concepts
  • Requirements
  • Plans and availability
  • Quick start
Getting Started
  • Create or sign in
  • Add the Discord bot
  • Start setup with /setup
  • Select a Discord server
  • Connect a Roblox community
  • Confirm ownership
  • Choose a subscription
  • Configure Open Cloud
  • Complete setup
  • Recommended next steps
Setup Guides
  • Discord bot permissions
  • Roblox community connection
  • Roblox Open Cloud
  • Verification
  • Group and rank binds
  • Community permissions
  • Experience
  • Quotas
  • Welcome messages
  • Audit-log delivery
  • Events
  • Subscriptions
  • API keys
  • Divisions
Feature Guides
  • Member management
  • Profiles
  • Linked Roblox accounts
  • Experience and quotas
  • Ranks and group binds
  • Warnings
  • Suspensions
  • Blacklists
  • Medals and qualifications
  • Events and attendance
  • Audit logs and rollback
  • Analytics
  • Community permissions
  • Discord commands and actions
  • Pending join reviews
  • Custom bot branding
  • Discord server transfers
  • Privacy and account controls
  • Subscriptions and billing
Troubleshooting
  • Troubleshooting overview
  • Discord server is missing
  • Roblox community not found
  • Ownership cannot be confirmed
  • Bot permissions are missing
  • Discord role does not update
  • Role is above the bot
  • Verification fails
  • Open Cloud errors
  • Rank change fails
  • Profile does not sync
  • Command is unavailable
  • Action is not permitted
  • Subscription access is missing
  • Temporary service problem
API referenceClan Labs websiteOpen dashboard Support
Overview
  • Introduction
  • What is Clan Labs?
  • Core concepts
  • Requirements
  • Plans and availability
  • Quick start
Getting Started
  • Create or sign in
  • Add the Discord bot
  • Start setup with /setup
  • Select a Discord server
  • Connect a Roblox community
  • Confirm ownership
  • Choose a subscription
  • Configure Open Cloud
  • Complete setup
  • Recommended next steps
Setup Guides
  • Discord bot permissions
  • Roblox community connection
  • Roblox Open Cloud
  • Verification
  • Group and rank binds
  • Community permissions
  • Experience
  • Quotas
  • Welcome messages
  • Audit-log delivery
  • Events
  • Subscriptions
  • API keys
  • Divisions
Feature Guides
  • Member management
  • Profiles
  • Linked Roblox accounts
  • Experience and quotas
  • Ranks and group binds
  • Warnings
  • Suspensions
  • Blacklists
  • Medals and qualifications
  • Events and attendance
  • Audit logs and rollback
  • Analytics
  • Community permissions
  • Discord commands and actions
  • Pending join reviews
  • Custom bot branding
  • Discord server transfers
  • Privacy and account controls
  • Subscriptions and billing
Troubleshooting
  • Troubleshooting overview
  • Discord server is missing
  • Roblox community not found
  • Ownership cannot be confirmed
  • Bot permissions are missing
  • Discord role does not update
  • Role is above the bot
  • Verification fails
  • Open Cloud errors
  • Rank change fails
  • Profile does not sync
  • Command is unavailable
  • Action is not permitted
  • Subscription access is missing
  • Temporary service problem
  1. Docs
  2. /
  3. Feature Guides
Feature Guides

Issue and manage warnings

Record low, medium, or high-severity member warnings in Clan Labs and maintain a clear moderation history.

Last updated 3 September 2026

Warnings create a community-specific moderation record for a Roblox member. Each warning has a severity and description and can be reviewed later by authorised staff.

Issue a warning

Use a member profile or /warnings create:

  1. Verify the target Roblox identity.
  2. Choose Low, Medium, or High according to your published policy.
  3. Write a factual description. Explain the behaviour and relevant context without including secrets or unnecessary personal data.
  4. Review the target and submit.
  5. Confirm the warning appears in the member’s warning history and audit log.

The default requirement to warn a member is Officer. Your community owner can set a different minimum level.

Review, edit, or delete

Use /warnings view or the dashboard profile to inspect history. /warnings edit can correct a warning’s severity or description, and /warnings delete removes the selected warning where the user has permission.

Editing is better than deleting when the underlying moderation event still occurred. If community policy requires deletion, record the reason elsewhere in the approved process and confirm the deletion audit entry.

API v2 also supports listing, issuing, fetching, updating, and deleting warnings. Read-only integrations need warnings.read; writes need warnings.write. API requests still pass plan, community, and feature checks.

Write useful warning descriptions

A good description is specific and neutral, for example: Left an assigned event post without notifying the host. Avoid insults, speculation, account credentials, private conversations unrelated to the incident, or details that staff do not need.

Permission and availability messages

  • Warning - Insufficient Permission means your community level is below the configured requirement.
  • This command is not available on trial! means the trial blocks the moderation command.
  • A tier or inactive-subscription message means the community does not currently have access.
  • An account or member lookup warning means the target should be verified before trying again.

Warnings are not a substitute for suspensions or blacklists. Use a suspension for a time-limited restriction and a blacklist for an explicit user or Roblox-group exclusion.

PreviousRanks and group bindsNext Suspensions
On this page
  1. Issue a warning
  2. Review, edit, or delete
  3. Write useful warning descriptions
  4. Permission and availability messages