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

Review pending Roblox joins

Check, accept, or decline pending Roblox community requests and configure Pro automation in Clan Labs.

Last updated 3 September 2026

Pending-join review helps authorised staff process requests waiting in the connected Roblox community. The workflow checks the applicant against the community’s configured eligibility and moderation rules before changing Roblox state.

Review requests manually

Use the Clan Labs pending-join view or Discord:

  • /pendingjoin requests lists applicable requests.
  • /pendingjoin check evaluates a request without bypassing the configured checks.
  • /pendingjoin accept and /pendingjoin decline make an authorised decision.

The default requirement is HICOM. Roblox Open Cloud must allow group:read and group:write for the connected community.

A known direct user blacklist or membership in a blacklisted Roblox community can make an applicant ineligible. If Clan Labs cannot verify a condition because Roblox or another dependency is unavailable, it does not treat uncertainty as eligibility.

Automate checks

ProAutomatic Pending Join Reviews

Run the same guarded review on a 5, 15, 30, or 60-minute schedule with Clan Labs Pro, reducing repetitive staff checks while keeping uncertain requests pending.

Compare plans

In the Pro automation settings:

  1. Enable scheduled pending-join review.
  2. Choose a cadence of 5, 15, 30, or 60 minutes.
  3. Set the available grace-period option so very recent requests are not processed too early.
  4. Decide whether requests known to be ineligible should be declined automatically.
  5. Save, then monitor the next scheduled result and audit activity.

The automation uses the same checks as Check All Requests. A request that cannot be verified remains pending for a later run. This fail-closed behaviour avoids accepting someone simply because an external check timed out.

If the schedule controls are not shown, the feature is not currently available to that community. If the controls are present but no run occurs, keep the time, community ID, last-run state, and any visible error for support.

Safety guidance

  • Keep the Open Cloud key scoped to the intended Roblox group.
  • Start with automatic decline off until the community validates its rules.
  • Review group blacklist entries before enabling broad automation.
  • Do not repeatedly accept a request after a timeout; refresh the pending list first.
  • Use the audit log to distinguish staff and scheduled decisions.

For credentials, see Connect Roblox Open Cloud. For service failures, use Open Cloud errors.

PreviousDiscord commands and actionsNext Custom bot branding
On this page
  1. Review requests manually
  2. Automate checks
  3. Safety guidance