Applications

Build custom application forms, publish them, and review submissions.

1 - Introduction

Applications let you create custom forms for staff recruitment, department onboarding, and other structured intake workflows.

Each application has a public ID, schema, settings, permissions, open or closed state, submissions, review history, and optional role/message automation.

Use Applications when you need consistent questions and review decisions. They are better than Discord tickets for repeatable intake because every applicant answers the same fields and reviewers can filter, approve, reject, and track status from the panel.

Each application is independent. You can run one form for staff recruitment, another for supervisor applications, and another for department transfers, each with different permissions and review behavior.

1.1 - Table of Contents

Section What it covers

Creating Forms Editor, field types, and publishing

Reviewing Submissions Approve, reject, staged results, and notifications

Settings Application-specific settings

Troubleshooting Common form and permission issues

1.2 - Links to Related Documents

2 - Creating Forms

Open Applications and click Create Application. Provide a name and optional description, then edit the Questions tab.

The editor autosaves schema changes after a short delay. The public form URL uses the application public ID and can be copied from the editor.

Start with the minimum questions needed to make a decision. Long forms reduce completion quality, especially on mobile. Use sections to group related questions and use required fields only when the answer is truly needed.

Test the public form before announcing it. Submit a test response, review it, and make sure role actions and notifications behave the way you expect.

type: form
title: Staff Application
meta: Public form preview
status: Accepting responses
fields:
- Discord Account | Required
- Roblox Username | Required
- Why do you want to join staff? | Long answer
- Preferred Department | Dropdown

2.1 - Field Types

Field type Use it for

text Short free-text answer.

textarea Long answer with optional rows.

email Email address input.

number Numeric input with min, max, and step.

select Dropdown, optionally multiple.

checkbox Multi-choice checklist.

radio Single-choice list.

date Date input with optional min and max.

discord_user Discord user field.

roblox_user Roblox user field.

section Non-answer content separator.

slider Numeric slider with min, max, and step.

2.2 - Publishing

Applications are closed by default. Turn on accepting responses in settings to make the form live.

Applicants submit through the public application page. CADLY saves answers, status, optional Roblox account details, and input metrics where available.

Closing an application stops new submissions but does not delete existing ones. Use this when a hiring window ends or when you need to edit questions without receiving partial answers during the change.

If you change questions after receiving submissions, older answers keep their original question structure. Avoid deleting major questions mid-cycle unless you are comfortable reviewing mixed submissions.

3 - Reviewing Submissions

Submissions start as submitted. Reviewers can approve or reject with optional review notes.

When stage responses is enabled, decisions are staged first and released later. This lets you review privately before publishing outcomes.

Use staged responses when several reviewers need to discuss applicants before results go out. Without staging, approval and rejection side effects can apply immediately.

Review notes should be professional and concise. They may be visible through configured messages depending on your templates, so avoid private staff discussion in the applicant-facing note.

3.1 - Real-Time Updates

Application lists update in real time when forms change, submissions arrive, or reviews are completed.

type: record
title: Submission review card
meta: Applications > Staff Application
status: Submitted
items:
- Applicant | @RiversideUnit
- Roblox | RiversideUnit_42
- Reviewer | Unassigned
- Result | Awaiting decision

4 - Settings / Configuration

4.1 - Response Settings

Accepting Responses

Controls whether the public application accepts submissions. Default: off | Requires: none

Stage Responses

Keeps review decisions staged until they are released. Default: off | Requires: none

Collect Roblox Account

Collects Roblox account information with submissions. Default: off | Requires: none

Enable this for ER:LC staff or department applications where in-game identity matters. Leave it off for forms that do not need Roblox identity.

Allow Reapply

Allows users to submit again after a final decision. Default: on | Requires: none

Disallow Form Editing

Prevents applicants from changing their answers after their first submission while it is awaiting review. Default: off | Requires: none

Cooldown Days

Days a user must wait before reapplying. Default: 0 | Requires: none

Banner Image URL

Optional public form banner image. Default: none | Requires: none

4.2 - Applicant Requirements

Require Discord Membership

Requires the applicant to be a member of the Discord server. Default: on | Requires: none

Minimum Account Age Days

Minimum Discord account age required to submit. Default: 0 | Requires: none

Required Roles

Roles a member must have to submit. Default: none | Requires: none

Blacklisted Roles

Roles that block submission. Default: none | Requires: none

4.3 - Review Actions

Give Roles on Submission

Roles added immediately after submission. Default: none | Requires: none

Give Roles on Approval

Roles added after approval. Default: none | Requires: none

Remove Roles on Approval

Roles removed after approval. Default: none | Requires: none

Give Roles on Denial

Roles added after denial. Default: none | Requires: none

Remove Roles on Denial

Roles removed after denial. Default: none | Requires: none

4.4 - Notifications and Access

Logs Channel

Channel for application activity. Default: none | Requires: none

Response Ping Role

Role pinged when a new response arrives. Default: none | Requires: none

Results Channel

Channel where approval or denial results can be posted. Default: none | Requires: none

Manager Roles

Can manage the application, review responses, and delete responses. Default: none | Requires: none

Manager roles should be limited to trusted leadership because they can alter settings and delete responses. Use reviewer roles for staff who only need to process submissions.

Reviewer Roles

Can view and review responses. Default: none | Requires: none

Viewer Roles

Can view responses read-only. Default: none | Requires: none

5 - Troubleshooting Common Issues

5.1 - Applicants Cannot Submit

Check accepting responses, Discord membership requirement, required roles, blacklisted roles, and cooldown.

5.2 - Application Is Locked

The form may be over the free-plan limit after Server PRO expires. Delete locked applications or restore Server PRO.

5.3 - Review Buttons Are Missing

Give the reviewer an application manager or reviewer role, or grant the global Applications Manage permission.

6 - Getting Support and Resources

If you need help, several resources are available:

Browse all CADLY documentation