Getting Started

This guide is optimized for first-day momentum. Follow the sequence and you will avoid most setup friction.

First 15 Minutes (All Users)

1. Sign in at Login or create an account at Register.
2. Confirm you land on Home and can open Account.
3. In Settings, set your display name, username, and avatar.
4. In Notification Delivery, verify push/email preferences.

Navigation Model (What Each Tab Is For)

• Home: cross-hub snapshot of what matters now.
• Hub: your active community workspace.
• Chat: direct + channel conversations.
• Tickets: your ticket wallet and transfer actions.
• Account: profile, photos, invitations, purchases, preferences.

Choose Your First-Week Path

Member path

1. Join one or more hubs from All Hubs or a share/invite link.
   • If you open a join link while signed out, attribution from the link is preserved after login.
2. Review upcoming events in your active hub.
3. Buy a ticket and complete required forms before event day.
4. Track updates in Alerts and Chat.
5. Use My Tickets and Purchase History as source-of-truth.

Organizer path

1. Create your hub from Create Hub.
2. Set join policy, decide whether members can share join links, and assign governance roles.
3. Create a draft event, then configure tickets and required forms.
4. Assign event staff with explicit permissions.
5. Publish only when event details and readiness controls are final.

Staff path (scanner, attendance, event operations)

1. Confirm your event staff role and permissions with the organizer.
2. Review scanner readiness and required form policies before event day.
3. Run check-in only from approved scanner surfaces.
4. Escalate blockers with exact ticket/state context.

First Event Readiness Checklist

• Event date/time/location finalized.
• Ticket types and capacity reviewed.
• Required forms published (including guest flow where needed).
• Staff roles assigned and tested.
• Event update flow tested for critical announcements.

Avoid These Early Mistakes

• Publishing before required forms are attached and versioned.
• Giving OWNER role too broadly instead of using ADMIN.
• Ignoring push/email delivery setup until event day.
• Treating alerts and chat as interchangeable workflows.

Continue With

• Hubs and Community Setup
• Events and Tickets
• Roles and Permissions