Details

Overview

Details is the identity page for an event. It controls the public event name, internal staff name, event dates, venue text, event status, cover image, and description that other pages rely on.

Use this page before configuring registration products or publishing the event. If Details is wrong, every downstream page can appear correct in the dashboard while attendees still see the wrong public information.

Dashboard route

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

Inputs and controls

Input or control	What it changes	Before saving
Event image	Uploads the A4 landscape image shown on event listing cards and the rego page. The source accepts JPG, PNG, and WebP images up to 5 MB.	Confirm the crop, mobile readability, public rights, and that the image is current.
Upload image	Opens the image upload/crop flow.	Wait for upload completion before saving.
Remove image	Clears the event image.	Use only if the public page should intentionally have no image.
Public name	Required attendee-facing event name.	Confirm spelling, year, and capitalization with the event lead.
Internal name	A private staff label used when operators need a clearer internal distinction.	Use only staff-safe context; do not put sensitive notes here.
Description	Markdown-ext attendee-facing copy shown on the rego page.	Check headings, links, and tone as public copy.
Venue name	Public venue label used on the rego site and Google Wallet pass.	Match the venue name used in announcements and passes.
Venue address	Public attendee-facing venue address.	Confirm privacy and safety expectations before publishing exact location.
Event status	Whether the event is draft, active, hidden, archived, or otherwise controlled by the dashboard state.	Do not set active until registration, payments, public copy, and staff ownership have been reviewed.
Start date and time	The event’s operating start.	Confirm timezone, venue schedule, age-check basis, and roster planning.
End date and time	The event’s operating end.	Confirm it matches closeout, check-in, volunteer, and public-page expectations.
Timezone	The timezone used to interpret event dates and windows.	Keep this consistent with registration, activity, volunteer, and coupon windows.
Event info card	Shows generated event metadata beside the form.	Use it to confirm the event ID and current saved state before editing.
Floating save bar	Saves or reverts dirty Details changes.	Do not navigate away while image upload or save is still in progress.

Image upload behavior

State or action	What happens	Operator impact
No image	The preview shows a No image placeholder.	The public page can still work, but the event will look unfinished in listings.
Upload image	Opens the cropper and uploads the cropped result.	The page shows an uploading state while the file is being processed.
Unsupported or too-large file	The page shows an image error.	Use JPG, PNG, or WebP below the 5 MB limit.
Remove image	Clears the image URL from the draft.	Save afterward if the event should no longer use the image.

Event info card

The side card is the quick identity check for the loaded event. Use it before saving if multiple tabs are open. It helps confirm that the Details form is still attached to the intended event record rather than a copied or stale URL.

Status options

Option	Meaning	Operational impact
Draft	Setup state for unfinished events.	Safest state while writing copy, building rego products, testing payments, and reviewing public pages.
Active	Public operating state.	Attendees may be able to view and use the event according to registration windows and page visibility.
Hidden	Keeps the event out of normal public discovery while preserving records.	Use when staff need direct-link testing or temporary suppression.
Archived	Post-event or retired state.	Use only after closeout obligations, refunds, settlements, and records are handled.

Timezone options

Option	Use when
Asia/Manila (PHT)	The event operates in the Philippines. This is the normal Furries PH default.
UTC	The event is intentionally coordinated in UTC or technical testing needs UTC.
America/New_York (ET)	The event operates on Eastern Time.
America/Los_Angeles (PT)	The event operates on Pacific Time.
Europe/London (GMT/BST)	The event operates in London time.
Australia/Sydney (AEST)	The event operates in Sydney time.

Save behavior

Details uses the floating save bar. Save writes the public name, internal name, markdown description, venue name, venue address, status, event start/end, timezone, and image state together. Revert restores the last loaded values.

If the public name is blank or required fields fail browser validation, save should not proceed. If the event date changes after other pages are configured, review registration windows, volunteer windows, activity windows, coupon dates, and roster day windows before activation.

Venue name, venue address, start/end date-time, and timezone are canonical event fields. Saving Details performs a safe partial merge and must not replace unrelated registration configuration. Date-time values round-trip in the selected event timezone rather than being reinterpreted as the browser’s timezone.

The save request includes the last known update timestamp. If another operator saved a newer version, the dashboard reports a conflict instead of overwriting it. Copy any draft text, reload the current event, compare the newer values, and then reapply only the intended change. The shared saving indicator clears when the conflict response arrives so the operator can recover.

Flowchart context

The Create an Event flowchart reaches Details immediately after the event shell is created. The final activation step also returns here because status changes are made from this surface.

Related setup pages: Payments Config, Rego Config, Google Wallet Config.

Common mistakes

The most common error is changing the event date after registration windows, volunteer windows, or activity deadlines have already been configured. If the event date moves, review every date-driven page before saving the public status as active.