Event Management Documentation

Start here

Event Management documentation now follows a product-docs structure: start with the overview, learn the concepts, follow task guides, then use reference pages when you need exact records, routes, or operating checks. Supabase separates getting started, product areas, reference, and resources; GitHub groups docs around user journeys and task areas. This section uses that same pattern for Furries PH operations.

Event Management helps teams create, publish, run, and close events while keeping attendee-facing information, staff work, money-adjacent records, and handoff notes aligned. The pages are written for people who may not be technical, so each guide explains what the area means, when to use it, what can change, and what proof should exist before handoff.

How this section is organized

Area	What to read it for
Foundations	Learn the operating model, accountability expectations, and meaning of event records.
Basics	Create an event, configure registration, run check-in, and close out cleanly.
Surfaces	Read screen-by-screen guides for event details, rego config, communications, payments, HR, Dealers Den, shop, inventory, POS, analytics, and snapshots.
Lifecycles	Understand how event, registration, payment, check-in, staff, and closeout states move.
Reference	Check communications, privacy, payments, role access, data records, route maps, and readiness expectations.

Recommended reading paths

New operator

1. Read the foundations page so dashboard words have plain-language meaning.
2. Follow one basics or getting-started guide with the real dashboard open.
3. Use the matching surface page before changing a live record.
4. Finish with the reference or checklist page so the handoff is reviewable.

Lead or administrator

1. Start from the lifecycle or workflow page closest to the problem.
2. Check records and role boundaries before authorizing a change.
3. Use the related links at the bottom of each page; they are generated from shared tags, so related pages stay connected even when navigation changes.

Support reviewer

1. Use search or tags to find the affected record, route, or surface.
2. Read the impact and handoff sections before interpreting a screenshot or export.
3. Ask for the proof listed in the guide before deciding whether a state is trustworthy.

Key pages

• Close Out an Event - Post-event workflow for reconciling money, records, inventory, staff notes, and attendee obligations.
• Configure Registration - Safe basics for tiers, add-ons, inclusions, group registration, forms, and publication readiness.
• Create an Event - Minimum safe workflow for creating an event before public registration opens.
• Run Check-In - Safe day-of-event check-in workflow, including scanner state, privacy, and offline readiness.
• Use an Event Shop - Attendee-facing event shop flow for browsing, persistent carts, checkout, payment, pickup, delivery, and order status.
• Shop Config - Event shop enablement, source-linked listings, standalone merch, selling limits, delivery couriers, and rate rules.
• Shop Orders - Shop order payment review, buyer-visible updates, internal notes, and fulfillment state.
• Shop Orders Dashboard - Shop-specific sales, platform-fee, logistics, delivery, claim, and item analytics.
• Shop Order Claim - QR/search workflow for releasing paid shop pickup orders.
• Forecasting - Registration, cash-flow, and production outlooks across practical planning horizons.
• Accounting - Event cash ledger, manual movements, evidence, reconciliation, and CSV review export.
• Attendee Communications Best Practices - How to safely preview, target, write, and send event communications.
• Check-In and Privacy Best Practices - How to protect attendee data and reduce day-of-event check-in mistakes.
• Event Setup Best Practices - Planning and review practices before event settings become public.
• Payments and Refunds Best Practices - How to keep payment instructions, balances, refunds, upgrades, transfers, and settlements auditable.
• Event Accountability - Why event operations require careful records, clear decisions, and review before changes go live.
• Event Records and Public Pages - How dashboard event records drive public registration pages and attendee-facing information.
• What Is Event Management? - Plain explanation of the Event Management System dashboard and the work it controls.
• Event Management Glossary - Plain definitions for Event Management System words, records, routes, and workflows.
• Check-In Lifecycle - Check-in preparation, live verification, offline operation, sync, and post-event review.
• Event Lifecycle - How an event moves from draft to setup, publication, live operations, and closeout.

Operating rule

Do not treat a dashboard page, route, file, or note as isolated. In event operations, one visible change can affect people, permissions, public information, records, and later review. Use the docs to connect the action to its owner, records, risk, and handoff proof.