Getting Started

This guide is optimised 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.
5. In Passkeys & MFA, add a passkey and set up authenticator MFA if your account policy requires it.

Navigation Model (What Each Tab Is For)

• Home: cross-hub snapshot of what matters now.
• Hub: your active community workspace.
• Chat: one inbox for direct messages, private groups, hub channels, and event channels.
• 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.

Organiser 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. Set up your core support channels from Chat and Notifications so members have a clear place to ask questions.
5. Assign event staff with explicit permissions.
6. Publish only when event details, channel setup, and readiness controls are final.

Staff path (scanner, Event Day, event operations)

1. Confirm your event staff role and permissions with the organiser.
2. Review scanner readiness, attendance registration policy, and required forms before event day.
3. Use Scanner as the main live door tool when scanning is enabled, and use Event Day for the full roster and attendance records.
4. Escalate blockers with exact ticket/state context.

First Event Readiness Checklist

• Event date/time/location finalised.
• 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.
• Waiting until event day to test passkey/MFA sign-in recovery paths.

Continue With

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