What this helps you do
You can invite staff and volunteers onto the team and give each one the right level of access, so they help without over-reaching. Each person signs in as themselves, so you always know who sent what. Dangerous actions, such as sending to everyone, changing roles, or leaving the Hub, ask for a fresh step-up confirmation with a passkey or an approval on the person's phone.
- Owner: everything, including billing, the Blasts account connection, and leaving the Hub.
- Admin: every audience, team management and integrations; no billing or account connection.
- Leader: sends to, and reads replies from, only the audiences you grant.
- Viewer: read-only reports and history.
When to use it
Use roles as soon as more than one department sends: public works owns closures and utility work, sanitation owns collection changes, parks owns facility notices, the clerk owns meetings and agendas, and the communications office or the public information officer holds the whole-town send.
How to do it
- Open Team.
- Invite a person by email and pick a role; they sign in with an email code or through the Blasts app.
- For a Leader, choose which audiences they can send to and which replies they can read.
- Review Access requests: people connected as members who asked for Hub access after signing in through Blasts. Nobody gets in unless you approve, and you pick the role first.
- In Settings, decide whether a leader's Blasts need an administrator's approval before they go out.
- Add a passkey on Home so step-up confirmations use Face ID, Touch ID or your device PIN.
Example
The communications director is the Owner. The clerk is an Admin. The public works superintendent is a Leader granted Public Works & Utilities and the route audiences; the recreation director is a Leader granted Parks & Recreation; the finance office is a Viewer. Public works posts the detour without waiting for anyone, and only the communications director and the clerk can send to All Residents, which asks for a passkey.
Good to know
- A Leader only sees replies from the audiences they are granted, so a question about a missed collection reaches sanitation and not the recreation director.
- Sending to All Residents or to Emergency & Urgent Operations, changing roles and removing users all require a fresh step-up confirmation.
- In Settings you can require an administrator's approval before a department lead's message goes out, which is often how a small office wants to start.
- The audit trail on Home records who sent, approved, invited or changed what, which matters when the question afterwards is who told residents and when.
- The Hub is not a records system. If a notice has to be retained, keep it wherever your municipality keeps records; messages here auto-delete after 30 days.