> ## Documentation Index
> Fetch the complete documentation index at: https://docs.technified.xyz/llms.txt
> Use this file to discover all available pages before exploring further.
# Applications
> Build application forms, collect submissions, and process them with your team.
The application system lets you create custom forms for recruiting staff, accepting players, or anything else. Members fill them out on your public page, and you review the submissions in the dashboard.
Open **Management > Applications** in the sidebar.
## Overview
The page shows three stats and a card for each form.
| Stat | Description |
| ----------------- | ------------------------------------- |
| Total Forms | Forms created, out of a max of 5 |
| Active Forms | Forms currently accepting submissions |
| Total Submissions | All submissions across every form |
Each form card shows its title, status, public badge, field count, submission count, and a public URL. From a card you can view submissions, edit the form, or delete it.
You can have up to **15 application forms** per server. Pause or archive old forms to free a slot. See [Limits](/limits) for all creation limits.
### Form status
| Status | Behaviour |
| -------- | -------------------------------------------------------------------------- |
| Active | Accepts submissions and appears on your landing page if public |
| Paused | Shows a "currently paused" message, no new submissions, existing data kept |
| Archived | Hidden from the public, all data preserved |
## Building a form
Forms use a drag and drop **Visual Form Builder** with four tabs: Build, Logic, Settings, and Preview. Forms support up to 25 questions, multiple pages, conditional logic, and undo and redo.
Click **New Form** for a blank form, or **Edit** on an existing card.
Drag a field type from the palette onto the canvas, then edit it in the inspector on the right.
Reorder fields by dragging, and add page breaks to split long forms into pages.
Use the Preview tab to walk through the form, then save. Set the status to Active when you are ready.
### Field types
| Type | Use it for |
| ----------- | ---------------------------------------------- |
| Short text | Names, usernames, single line answers |
| Long text | Detailed explanations |
| Dropdown | Pick one from a list |
| Radio | Pick one, all options visible |
| Checkbox | Pick several |
| Number | Age, hours per week, with optional min and max |
| Email | Validated email addresses |
| URL | Validated links |
| Date | Calendar picker |
| Time | Time picker |
| Static text | A read only info or rules block, no input |
Every field can have a label, help text, placeholder, a required toggle, options (for choice fields), and min and max (for number, date, and time).
### Multi-page forms and logic
Split the canvas into pages with page breaks. Applicants click **Next** to move forward, which is great for long forms.
On the **Logic** tab you define per-page rules: if the applicant answered a certain way, then skip to a page, jump to a page, or end the form. Rules are checked when the applicant clicks Next, and the first matching rule wins, so order them from most specific to most general.
### Settings
| Setting | Description |
| ------------------------ | -------------------------------------------------------- |
| Status | Active, Paused, or Archived |
| Notify staff on submit | Post a notice in your staff channel for each submission |
| DM applicant on decision | Message the applicant when approved or rejected |
| Create review channel | Open a private channel for staff to discuss a submission |
| Require verified Roblox | Only members with a linked Roblox account can submit |
| Allow resubmissions | Let users submit more than once |
| Cooldown (hours) | Wait time between submissions, 0 means none |
| Max submissions per user | Lifetime cap per user, 0 means unlimited |
Editing a form does not rewrite existing submissions. Deleting a form permanently removes the form and every submission attached to it. There is no undo.
## Managing submissions
Open a form and click **View Submissions** to see every response.
### Statuses
| Status | Meaning |
| --------- | ------------------------------------ |
| Pending | Submitted, awaiting review |
| In Review | A staff member has started reviewing |
| Accepted | Approved, applicant notified |
| Rejected | Declined, applicant notified |
### Processing a submission
Click a submission to see the applicant's accounts, every answer, and the status timeline.
Click **Mark In Review** so your team knows you are on it.
Click **Accept** or **Reject**. Add an optional message or reason. The applicant receives a Discord DM.
You can filter by status, sort newest or oldest first, and search by Discord or Roblox username.
## Best practices
* Keep applications focused. 10 to 15 questions is plenty for most teams.
* Use the **Static text** field for rules instead of a "did you read the rules?" question.
* Use **Logic** to end the form early when an applicant does not qualify.
* Review applications within a couple of days and set them to In Review while you work.
* Apply the same criteria to everyone, and give a short reason when you reject.