Applications
Growing your team is easy with Zander's application system. Showcase open roles on your website, let players apply with one click, and keep listings organised from the dashboard - all without managing a separate recruitment tool.
📸 Screenshot: The /apply page showing open application cards with icons, descriptions, and "Apply" buttons
For Players​
Open applications are listed publicly at /apply. Each listing shows:
- The role or position name
- A description of what the role involves
- The requirements for applying (Markdown-formatted)
Applications with a closed status are shown as closed with no apply action. Click Apply on any open listing to go to the application:
- If the application is linked to a Zander Forms form, you're taken to
/forms/<slug>to fill it out in-platform. - Otherwise, you're taken to an external Redirect URL (Google Form, Typeform, custom URL, etc.) in a new tab.
No login or permission is required to view or apply from this public page.
Use the Discord /apply command to get a quick link to the applications page without leaving Discord.
For Staff​
Applications are managed from Dashboard → Applications (requires zander.web.application).
📸 Screenshot: The applications dashboard showing a list of active applications with edit/delete controls
Creating an Application​
From the dashboard, click Create and fill in the following fields:
| Field | Description |
|---|---|
| Display Name | The role or position name shown on the listing card |
| Description | A short summary of the role or opportunity |
| Display Icon | Icon shown on the listing card |
| Requirements | Markdown-formatted list of requirements for the role |
| Type | external (send applicants to a Redirect URL) or linked_form (send applicants to an in-house Zander form) |
| Redirect URL | Where applicants are sent when they click "Apply" - used for external type (Google Form, Typeform, custom URL, etc.) |
| Linked Form | Which Forms form to submit through - used for linked_form type |
| Position | Display order on the applications page - lower numbers appear first |
| Status | Whether the application is open or closed |
external application submissions are not stored in Zander - the Redirect URL points to wherever you collect responses. linked_form applications are stored in Zander, as regular Forms responses; see Forms for how those responses are reviewed. Either way, Zander manages the listing display.
Managing Listings​
- Reorder listings by adjusting the position number.
- Edit any field, including switching between
externalandlinked_formtype. - Close an application by setting its status to closed - it disappears from the public page but is preserved in the dashboard.
- Delete listings you no longer need.
Every create, edit, and delete is written to the audit log.
API Reference​
This section is for developers integrating with Zander directly; if you're just using the dashboard, you can skip it.
Base path /api/application.
| Method | Path | Auth | Request | Response |
|---|---|---|---|---|
| GET | /api/application/get | apiKey bearer, feature-flag gated | Query: id (optional) | { success, data: [...] } - includes linked form name/slug/status where applicable |
| POST | /api/application/create | apiKey / dashboard session (zander.web.application) | actioningUser, displayName, description, displayIcon, requirementsMarkdown, position, applicationStatus, applicationType, redirectUrl, linkedFormId | { success, message } |
| POST | /api/application/edit | same | same fields + applicationId | { success, message } |
| POST | /api/application/delete | same | actioningUser, applicationId | { success, message } |
Feature Toggle​
"applications": false
Turning this off hides the /apply page and makes the Discord /apply command tell users the feature is unavailable.