Administration

Setting up your team and configuring Crowd for your event. These tasks need an administrative role, usually Admin or Dispatch.

Staff

Manage your roster under Staff. For each person you can set:

Name, email, and call sign — the email is their login; the call sign shows on the board and in the field.
Title — Dispatcher, Supervisor, Responder, Medical, or Security (a label, shown with a color).
Role — what they can actually do (see Roles & permissions below).
Phone number — used for SMS notifications.

You can also mark someone on/off duty, deactivate an account (revokes access without deleting their history), and send a password reset. New accounts get a temporary password and are prompted to set their own on first sign-in.

On-duty matters "On duty" drives who's counted as available and who receives all-call messages. Have staff toggle their status at shift start/end (they can do it from their own Profile).

Roles & permissions

A role is a named bundle of permissions; every staff member has one. Crowd ships with sensible system roles (Admin, Dispatch, Field Responder, Medical, Security, Observer, ConOps), and you can create your own. Edit roles under Admin → Platform Settings; each permission has a plain-language description next to it.

How incident visibility works

Incidents use three distinct permissions — this is the part worth understanding:

Permission	Grants
incidents:read	Open and read the details of an incident the person is on (created, assigned, or granted). Not a view of everything.
incidents:list	See the full incident list / board — every incident, not just their own.
incidents:read_all	Open the details of any incident, regardless of assignment.

So a field responder with only read sees their own calls; give a role list to let it see the whole board; add read_all to let it open any incident's details. (Dispatch and Admin already include all of these.)

If a change doesn't show up Crowd refreshes a signed-in user's permissions when they next open the app — no logout needed. If someone has an older session open, having them reopen Crowd picks up the new role.

Other permission groups

PCR (medical): read is limited to reports a person authored or whose incident they're assigned to; read_all is medical oversight (every report). Plus create, update, delete, and grant-access.
Tickets, Messages, Conversations, Staff, Audit, System — each a group of create/read/update/etc. permissions.
Break-glass (incidents:break_glass, pcr:break_glass) is an entitlement, not its own role. Attach it to any role that may need emergency access to restricted records. Every break-glass is logged.

Least privilege Give each role only what it needs. Volunteers rarely need delete or read-all; reserve break-glass for people you trust to use it in a real emergency.

Platform settings

Under Admin → Platform Settings you can tune:

Tones — announcement threshold: the minimum priority that triggers a spoken announcement on the Aurora Tones Display.
Tones — voice: the spoken voice used for read-outs.
Two-factor policy: whether 2FA is optional or required for everyone.
AI features: a master switch for AI triage suggestions (see below).

AI triage optional

Crowd can suggest a category and priority from a short description when an incident is created, and flag a likely emergency. The suggestion is a starting point; a dispatcher confirms or changes it before saving. It's never applied to medical reports. One switch turns all of this on or off, and when it's off there's no sign of it anywhere in Crowd. Before enabling it, review AI Product Use for exactly what data is sent and where it goes.

Audit log

The Audit view records security-relevant actions — logins, password and 2FA changes, role assignments, and break-glass events — with who, when, and from where. Use it to review access and investigate after the fact. Break-glass on a restricted record also raises a real-time alert to oversight roles.

Notifications

Assignment and all-call notifications work out of the box. Individual responders turn on push notifications per device from their Profile in Voyager (iPhone users must install Voyager to the Home Screen first). Assigned staff with a phone number also receive SMS.

← Aurora — displays Almanac home →