Create applications and review responses

Applications let verified Roblox users apply to your community before they join it. Forms and staff review are available on every plan; automatic grading requires Pro. Community access, account restrictions, and staff permissions still apply.

Create and share a formCopy link to Create and share a form

1. Open Manage → Applications and select Create application.
2. Enter a name and introduction. Add short text, long text, single-choice, or multi-select questions, and mark the required questions.
3. Choose staff review or automatic grading. Add an application password if you want to restrict who can open the questions.
4. Save, then use the application's share button to copy its link.

Forms support 1–50 questions. Short text answers allow 500 characters and long text answers allow 10,000. Choice questions support 2–30 options. Expand a question to edit it and use its drag handle to reorder it.

Manage application forms defaults to Owner. Review application responses defaults to Officer. These permissions are separate: managing forms does not grant access to responses. Owners can configure both on the Permissions page.

Never request or include personal information in questions, options, or answers. Clan Labs rejects detected sensitive information with a generic validation message, but pattern checks cannot identify every kind or disguise of personal information.

Apply using a verified accountCopy link to Apply using a verified account

Applicants sign in to Clan Labs, choose a verified Roblox account, and open the shared link. A password-protected application immediately shows an unlock modal with the application, community, and selected account. Its background preview does not expose the real questions.

Applicants answer one question at a time using Back and Next, with a question counter and progress bar. A red asterisk marks required questions. Required or flagged answers block advancing; Submit application stays disabled until all required answers are valid. Optional questions may be skipped, but the entire response cannot be empty.

Answers remain while moving between questions in the current draft. Switching verified accounts or reopening a changed form clears that draft. Each Roblox account can submit once per saved application version.

Grade automaticallyCopy link to Grade automatically

Every question must be required and use single-choice or multi-select answers with a correct answer marked. Leniency sets how many questions may be wrong out of the total; at least one correct answer is required. Questions have equal weight. A multi-select answer must match the complete correct set, with no missing or extra choices.

If Pro access ends, new submissions wait for staff review. Saved answer keys and previous decisions remain intact.

Templates and duplicationCopy link to Templates and duplication

Select Create application to open the normal editor when there are no community templates. When templates exist, choose one or start blank from the template picker. Review and edit every question before opening the form.

In the editor, select Save as template beside Create application (or Save changes) to save the current draft as a community template. This validates the form and uses its application name as the template name, without creating or updating an application.

Use Duplicate application on a card to open an editable copy. Use Save as template to name and store that application's current form content for your community. Saved templates appear in the creation dialog, where you can also delete them. Deleting a template leaves existing applications intact.

Copies and templates preserve questions, options, answer keys, and grading settings. New forms start closed and receive their own ID and version when saved. Passwords, responses, and join requirements are never copied. Changes to a template or source application do not affect applications already created from it. Automatic grading still requires active Pro access when creating the new form.

Community templates are private to staff with application configuration access. To revise a template, save the updated application as a new template and remove the old one.

Review responsesCopy link to Review responses

Select Review responses on an application card. Filter by Awaiting review, Passed, Failed, or all responses, then select an applicant. The inbox shows the Roblox headshot, username, submission date, version, and result.

The applicant list and response pane scroll independently. Applicant pages contain up to 25 responses, and answer pages contain up to five questions. On a narrow screen, use Back to applicants to return to the list.

For a pending response, optionally enter a private review note and Feedback to applicant, then choose Pass or Fail. Feedback is shared with the applicant; private notes remain staff-only and are never copied into feedback. Each field allows up to 2,000 characters. Do not include personal information in feedback. A decision is final for that response, and staff cannot review their own submissions. Applicants cannot see staff notes or answer keys. Reviewers who own a response also cannot see its private staff notes.

Receive a decisionCopy link to Receive a decision

A new passed or failed decision creates a dashboard notification and queues a Discord DM for the Discord account that submitted the response. This also applies to automatic grading and trusted API submissions. Pending responses do not generate a decision notification.

Open the dashboard bell to see the notification dropdown. Use Load more for older results or Mark all as read to clear unread indicators. Selecting a notification opens its result modal without leaving the current page and marks it read. The Discord View result link opens the same result after sign-in.

Messages identify the community, application, and outcome without exposing answers or private staff notes. Optional staff feedback appears in the result modal, reached through the dashboard notification or Discord View result link. It also appears when the original applicant checks their result on the application page. Feedback remains tied to the submitting Discord account if Roblox ownership changes. If Discord cannot deliver the DM, the dashboard notification remains available. Historical decisions are not backfilled into notifications.

Require a pass before joiningCopy link to Require a pass before joining

Open Pending Join → Required applications, select the forms, and Save. Reset restores the saved selection. Every selected form needs a pass for the exact Roblox account requesting admission.

Missing, failed, unreviewed, or temporarily unavailable application results leave the Roblox request pending, even when automatic decline is enabled. Passing an application does not itself accept a Roblox join request. Remove and save a requirement before closing or deleting its form.

See Pending join reviews for the separate approval workflow and plan requirements.

Versions, deletion, and rollbackCopy link to Versions, deletion, and rollback

Saving a form publishes a new version. It does not wipe previous responses: they keep their submitted questions and decisions. An earlier pass continues to satisfy that application's join requirement. Deleting a form closes its link but preserves historical responses for data export and erasure.

To remove responses, staff need both form-management and response-review permissions:

• Clear all responses permanently deletes responses across every version, regardless of the current filter.
• Select up to 100 individual responses and choose Delete selected for granular deletion.

Check the count and type the application name to confirm. If the form or submissions change before confirmation, reopen the dialog. Deletion preserves the form, removes related notifications and queued DMs, and allows a new submission when the current-version response was deleted. Deleted passes no longer satisfy join requirements. Response deletion is audited and cannot be rolled back.

Form creation and updates also create audit entries. Eligible individual audit rollback can reverse creation or restore an edit as a new version within 30 days. It preserves responses and join requirements, refuses conflicts with later changes, and cannot close or remove a required form. Application changes are excluded from batch rollback.

Resolve a blocked applicationCopy link to Resolve a blocked application

What happens	What to do
Password is rejected	Ask community staff for the current application password.
An answer cannot be accepted because it contains sensitive information	Remove personal or sensitive information and rephrase the answer. Do not try to disguise it.
Submit is disabled	Complete all required answers and correct flagged fields. At least one answer must be present.
The form changed while answering	Reopen the current version and answer it again; the old draft is cleared.
A response already exists	Check the result for the selected account and version. A new form version permits another attempt.
A passed applicant is still pending in Roblox	Check every required application for that exact account and review the separate Roblox join request.

Application responses and notifications participate in personal export and erasure. For integrations, see Applications through the API.