Roles & Access
How access works across the three Destination Hunts surfaces — organizer accounts in the admin portal, facilitators, anonymous players, and display screens.
Destination Hunts has four kinds of actors, each with its own access model.
Admin portal: organization users
The admin portal is for authenticated members of an organization (accounts are managed through Clerk). Every action is scoped to your active organization — you only see and manage your own org's events, libraries, and templates.
Three roles exist:
| Role | Identifier | Who it's for |
|---|---|---|
| Admin | org:admin | Full organization management — invitations, role changes, member removal, plus everything a Member can do. |
| Member | org:member | Standard organization member. |
| Hunts Admin | org:hunts_admin | Internal Destination Tours org only — external collaborators who need hunts access without organization-membership management. |
Admin-only actions on the Team page: sending invitations, changing roles, and removing members. Invitations expire after 30 days and can be resent (with a 60-second cooldown per invitation) or revoked. A last-admin protection blocks demoting or removing the final admin of an organization.
The Hunts Admin pinning rule
Hunts Admin exists only inside the internal Destination Tours
organization. When an admin of that org invites someone whose email is not
@destinationtours.com, the server pins the invitation to Hunts Admin
regardless of the role selected — the invite still succeeds, just with the
only role an external partner may hold. The invite dialog states this
directly: "People outside @destinationtours.com join the Destination Tours
organization as Hunts Admin (hunts access only)." This prevents an invite
typo from handing an external collaborator internal access. Hunts Admins run
hunts; they do not manage org membership.
See Organizations & Team for the full member-management workflow.
Facilitators
Today, facilitator actions are available to organization users: any authenticated member of your org can act as a facilitator on events your org owns — reviewing photo/video submissions, answering the help channel, marking roadblocks complete, force-activating challenges, and applying game-master effects. A dedicated, scoped facilitator role is future work.
There is a second, mobile-side flavor of facilitator: staff teams. A team flagged as staff (the Staff badge on the Teams tab) plays through the mobile app like any team, but is excluded from the leaderboard, never counts toward a challenge's Max Completing Teams cap or speed-bonus positions, and unlocks Facilitator Tools in the app's Settings for applying effects to player teams.
Players: no accounts
Players never create accounts. Joining a hunt takes exactly three things: a display name, a 6-character team code, and the device itself (a device ID the app generates). On join, the server issues a team-member token scoped strictly to that player's own team and event — a player can never read or act on another team's data.
The token expires 24 hours after the event's end time (so teams can review results afterward), with a minimum lifetime of 1 hour. When it expires, the app returns to the Join screen. See Joining a Hunt.
Display screens (kiosk mode)
For venue TVs and projectors there is a separate read-only display token: event-scoped, no write access, with a 90-day lifetime. It powers the standalone display view (leaderboard/slideshow screens) without exposing any admin or player capability.
Quickstart: Your First Hunt
A start-to-finish walkthrough for organizers — build an event, add challenges and teams, publish, run it live, and end it.
Organizations & the Team Page
Manage who can access your organization — members, roles, invitations, and the special rules for external collaborators in the Destination Tours organization.