Community admin guide

Tell us about your community — what it is (school, sports club, neighbourhood group, faith community, camp), roughly how many families, and what trips you'd use HALO for first. We onboard a handful of communities at a time so each launch gets attention.

Once approved, we provision your community on HALO and grant you the community-admin role. You get a clean dashboard scoped to your community only — you cannot see another community's drivers or parents, and they cannot see yours.

Your community gets a unique join code. Parents and drivers join HALO by entering it. The code is not a secret URL — it's deliberately a short string so you can read it out at a parents' evening or print it on a flyer.

Drivers upload a current licence and proof of insurance. You review the documents inside the admin console. Approve to grant the verified-driver badge; decline with a reason if anything is missing or wrong. Approvals and declines are recorded in the audit log.

Parents register their children with verifiable consent. You see the family and confirm they belong to your community. Approve, decline with a reason, or ask a follow-up question — the parent gets the message in-app and via email.

The admin dashboard shows live ride counts, CO₂ saved, the active driver list, and recent incidents. The numbers are scoped to your community — they're a number your community can be proud of, not a global vanity stat.

When a parent presses SOS during an active ride, the admin dashboard surfaces the live location of the ride and the contact details of the driver and the family. You decide whether to call the driver, call the family, escalate to the platform team, or call emergency services directly. SOS calls are recorded to the audit log.

Every privileged action — approvals, declines, suspensions, SOS responses, account deletions — is recorded to an append-only audit log. The log is visible to you (your community's scope) and to the platform team. Retention windows are documented in the privacy policy.