Review pending Roblox joins

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 manuallyCopy link to Review requests manually

Use the Clan Labs pending-join view or Discord:

• /pendingjoin requests lists applicable requests.
• /pendingjoin check immediately reviews every pending request. It accepts eligible applicants, declines applicants who fail a configured requirement, and leaves requests pending when a check is unavailable.
• /pendingjoin accept and /pendingjoin decline make an authorised decision about one request.

The dashboard’s Check All Requests button performs the same bulk operation after showing a confirmation. The Discord command starts the review as soon as it is submitted.

The default action requirement is HICOM. The community's Roblox connection must be operational, and the authorizing account must retain permission to read and decide pending joins.

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.

When shared Roblox scheduling is enabled, a review can save decisions while waiting for Roblox capacity. A queued decision has not completed yet. Follow Check status in the bot or open Roblox operations in the dashboard to see its outcome. Each decision belongs to the request that was reviewed; withdrawing it and submitting a new request requires a new decision.

Individual decisions wait briefly for a confirmed result. If processing takes longer, the saved request continues after the response returns. Check its status before submitting another decision. Roblox operations refreshes every two seconds while the visible page has active requests, and every fifteen seconds otherwise.

Require passed applicationsCopy link to Require passed applications

Under Pending Join → Required applications, select the forms that applicants must pass, then Save. Selections stay in the draft until saved; Reset restores the saved settings. This uses the pending-join configuration permission.

Every selected application needs a pass for the exact Roblox account requesting admission. An earlier-version pass remains valid. Missing, failed, unreviewed, or temporarily unavailable results leave the join request pending, including when automatic decline is enabled. These requirements apply to manual, bulk, and scheduled approval workflows.

Passing an application does not automatically accept the Roblox request. Remove and save a requirement before closing or deleting its form. Deleting a passed response removes its eligibility benefit. See Applications to create forms and review responses.

Explore the applications and recruitment workflow to see how forms and staff review fit into admission.

Changes to required applications are audited but cannot be reversed through audit rollback; edit and save Pending Join settings to change them.

Recover a partial reviewCopy link to Recover a partial review

A bulk review can process requests before the Roblox connection fails. The bot reports how many were processed and leaves the remaining requests pending. Completed decisions are not automatically reversed.

Record the processed count, restore authorization if required, then refresh the pending list before resuming. For a temporary connection failure, allow the service to recover. Do not repeat an uncertain individual decision until you have checked Roblox state.

Automate checksCopy link to Automate checks

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.

Scheduled reviews also require an operational Roblox connection. Reconnect when explicitly required, or allow a temporary refresh/provider failure to recover. The automation uses the same checks as Check All Requests. A request that cannot be verified remains pending for a later run, so an external timeout cannot make an applicant eligible.

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.

Start with automatic decline off and review group blacklists before enabling automation. Check the audit log to distinguish staff and scheduled decisions.

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