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 person sends: a volunteer coordinator running call sheets, a track chair handling session and speaker changes, an operations desk that answers attendees on event day, or a sponsor who should read along without sending.
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 organizer invites the operations manager as an Admin, the volunteer coordinator as a Leader granted the volunteers audience, and each track chair as a Leader granted their own track. On event day the track chair moves a session without waiting for anyone, the volunteer coordinator fills a gap at the registration desk, and only the organizer can send a gate change to All Attendees, which asks for a passkey.
Good to know
- Grants are per audience and cover sending and reading replies separately, so a track chair can answer their own attendees without seeing the whole event inbox.
- Sending to All Attendees, changing roles and removing users all require a fresh step-up confirmation.
- Set up the team and the grants before event week: on the day itself nobody has time to work out who can send what.
- The audit trail on Home records who sent, approved, invited or changed what.