Activities

Overview

Activities creates event-specific submission forms. These can represent panels, conbook entries, performances, workshops, or any other application/submission flow the event needs.

Each activity becomes its own attendee-facing submission surface on the rego site. The activity card controls the label, URL slug, availability window, public copy, and full form schema used to collect answers.

Dashboard route

• /ems/manage/activities?id=:eventId

Page controls

Input or control	What it changes	Before saving
Add activity	Creates a new activity draft with one starter question, Open submission as the button text, and Active turned on.	Confirm the form has an owner, review path, and public purpose before saving.
Empty state	Shows No activities yet. when the event has no activity forms.	Add an activity only when the event is ready to collect that kind of submission.
Floating save bar	Saves all changed activity cards or reverts to the last loaded snapshot.	Revert if a form was edited on the wrong event or if question structure was changed accidentally.
Activity status line	Shows save, upload, or unsaved-change messages.	Read errors here after uploads or saves fail.
Collapse / Expand	Hides or restores a card’s configuration body without deleting its draft.	Collapse completed cards when managing several activity forms.

Activity card controls

Input or control	What it changes	Before saving
Active	Controls whether this activity can be used on attendee-facing surfaces.	Keep off for drafts, old calls for submissions, or forms still waiting for terms.
Up	Moves the activity higher in saved sort order.	Use when multiple activity buttons appear together.
Down	Moves the activity lower in saved sort order.	Use to keep less-used forms behind primary calls.
Remove	Deletes the activity from the current draft.	Avoid removing an activity after submissions exist unless staff have confirmed how those records are handled.
Activity title	Names the activity for staff and attendee-facing contexts.	Use public wording, such as Panel Application or Con Book Submission.
Slug	Sets the last part of the activity URL. Blank slugs are generated from the title.	Keep it short and stable because shared links can break if the slug changes.
Button text	Sets the label used where attendees open the submission form.	Use action wording, such as Submit panel or Send conbook entry.
Question count	Read-only count of current questions.	Use it to verify that added sections and questions match the intended form size.
Description	Markdown-ext public description shown above the submission form.	Include eligibility, deadline context, rules, and what submitters should prepare.
Opens	Earliest date and time submissions can be created. Blank means available immediately.	Match announcements and reviewer availability.
Closes	Date and time submissions stop. Blank means the form stays open until manually disabled.	Close early enough for scheduling, layout, tech, or content review.

Submission form builder

Control	What it does	Before saving
Add question	Adds another field to the activity form schema.	Ask only for information reviewers or production teams will use.
Add section	Adds a section break or grouping to the form.	Use sections to separate applicant info, availability, content details, files, and acknowledgements.
Question label	Sets the prompt submitters answer.	Write in complete, non-technical language.
Helper text	Adds guidance below the prompt.	Use examples, accepted formats, limits, and review criteria.
Required flag	Prevents submission without an answer.	Require only fields needed for review or production.
Options	Defines choices for option-based fields.	Keep options mutually clear and avoid overlapping meanings.
Conditional paths	Shows fields only after matching previous answers.	Use to keep the form shorter for people who do not need follow-up questions.
Validation rules	Limits answer shape where supported.	Use for dates, numbers, emails, uploads, or constrained values.
Usernames	Collects one or more Furries PH usernames for co-panelists, collaborators, or other account-linked participants.	Set minimum/maximum selections; entries are normalized without @, deduplicated, and validated by the API.
Option image upload	Uploads image assets used by option-based questions.	Use public-safe images and wait for upload completion before saving.

Flowchart context

Create an Event links here when the event needs applications or submissions beyond registration. Active Event Workflow checks activity queues through Submissions Review and Approved Submissions.

Common mistakes

Do not open an activity before the review team agrees on what each answer means. A form can collect data quickly, but unclear questions create slow review later.

If an activity was opened too early, turn Active off, review existing submissions in Submissions Review, then reopen only after the form and terms are correct.

Username answers are shown only through the authorized submission review surfaces. Ask for collaborator usernames only when reviewers need them, explain why they are collected in helper text, and avoid requesting unrelated account identities.