Forms
Replace one-off Google Forms with forms that live inside your platform. Zander's form builder lets you create custom submission forms — for applications, feedback, event signups, or anything else — and delivers responses straight to a Discord channel or forum thread, with staff able to convert responses directly into support tickets.
📸 Screenshot: A published form page with multiple question blocks and a submit button
For Players
Submitting a Form
Forms are published at /forms/<slug>. Each form can be:
- Open — anyone can view and submit
- Login required — you must be signed in to submit
- Password protected — a staff-provided password unlocks the form
- Anonymous — your identity is not attached to the submission (when enabled by staff)
After submitting, you are taken to a confirmation page. If the form has submitterCanView enabled, you can return to view your submitted response at any time.
Your Responses
All your past form submissions are listed at /my/forms/responses. Click any entry to view the full response you submitted.
📸 Screenshot: The /my/forms/responses page showing a list of submitted form responses with dates and form names
For Staff
Creating a Form
- Go to Dashboard → Forms and click Create Form.
- Enter a name and slug (the slug determines the public URL:
/forms/<slug>). - Add form blocks — each block is a question or input field.
- Configure delivery options (see below).
- Save as a draft, then publish when ready.
📸 Screenshot: The form editor with multiple question blocks and delivery configuration options
Form Settings
| Setting | Description |
|---|---|
| Name | Display name shown at the top of the form |
| Slug | URL-safe identifier — sets the public URL to /forms/<slug> |
| Status | draft (not publicly accessible) or published |
| Require Login | Require the submitter to be signed in |
| Allow Anonymous | Allow submissions without attaching the submitter's identity |
| Access Password | Optional password to restrict who can open the form |
| Submitter Can View | Whether submitters can view their own response after submission |
Discord Delivery
When a response is submitted, Zander can notify Discord in two ways — configure one or both:
| Method | Setting | What Happens |
|---|---|---|
| Webhook notification | discordWebhookUrl + webhookEnabled: true | An embed is posted to the configured webhook URL |
| Forum thread | discordForumChannelId + postToForumEnabled: true | A new thread is created in the configured Discord forum channel containing the full response |
Both delivery methods are non-blocking — a failed Discord delivery does not affect whether the submission succeeds.
Viewing Responses
Go to Dashboard → Forms → <Form Name> → Responses to see all submissions. You can:
- Filter responses by status (
new,in_progress,resolved) - View each individual response in full
- Update a response's status
- Convert a response into a support ticket
Converting a Response to a Ticket
From any response detail page, click Convert to Ticket. This:
- Creates a new support ticket with the form data pre-filled
- Adds the submitter and converting staff member as ticket participants
- Posts a Discord embed in the ticket channel with action buttons
- Marks the form response as converted
Permissions
| Permission | Description |
|---|---|
zander.web.forms | Base access to the Forms dashboard |
zander.web.forms.<slug> | Access responses for the specific form (e.g. zander.web.forms.feedback) |
zander.web.forms.* | Access responses for all forms |
Use slug-specific permissions to give different staff teams access to only the forms relevant to them — for example, give your events team zander.web.forms.event-signup without exposing other forms.
Feature Toggle
"forms": false
Disabling this feature removes all /forms/ routes from the site and disables the Forms dashboard section.