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 when more than one person sends: an on-site manager who should reach only their own community, a maintenance manager who announces planned work, an assistant who posts amenity and parking notices, a board secretary who sends the owners' summary, a regional manager who oversees several communities, a bookkeeper who should see history but never 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
A management company invites the regional manager as an Admin, each on-site manager as a Leader granted only their own community's place audiences, the maintenance manager as a Leader granted Maintenance & Property Notices and the places, the board secretary as a Leader granted Owner & Association Updates, and the bookkeeper as a Viewer. Each community runs its own notices, and only the regional manager and the owner can send to All Residents, which asks for a passkey.
Good to know
- Managers, office staff, maintenance staff and board members are Hub team members with roles and per-audience grants. They are not a resident audience: there is no Staff or Board list on the preferences page, and a message to the team is a Team matter, not a Blast to an audience.
- The board is not all owners. A board member who needs to send gets a Leader role; owner-facing communication goes to Owner & Association Updates, which residents choose or you assign.
- A Blast shows the COMMUNITY, with your name and logo on it, not an individual manager or technician. There is no per-person sender identity in the Hub.
- A Leader only sees replies from the audiences they are granted, so a resident's reply about an entry time reaches the maintenance manager, not the board secretary.
- Grants are per audience and cover sending and reading replies separately, so an office assistant can answer a thread without being able to send to the whole community.
- A new community starts with approval off, so a manager's Blast goes out when they send it. Turn approval on in Settings if you want an administrator to review Leaders' sends first; it is separate from auto-accept, which decides whether a new connection is accepted automatically.
- Sending to All Residents, changing roles and removing users all require a fresh step-up confirmation, and a board member who connected as a resident and then asked for Hub access appears under Access requests until an admin approves and picks the role.
- The audit trail on Home records who sent, approved, invited or changed what, which matters when a board asks what went out and when.