Set up your first team and invite members
Glassbreak Team · Published 2026-07-19
Everything in Glassbreak is scoped to a team inside your organization: contacts, emergency messages, escalation rules, playbooks, and secrets all belong to a team. This guide covers creating one and bringing people in.
Responders vs recipients
Glassbreak distinguishes two kinds of people, and only one of them needs a paid seat:
- Responders are teammates with Glassbreak accounts. They sign in, send alerts, approve secret decryptions, run playbooks, and hold encryption keys. Responders occupy seats — this is what paid plans charge for.
- Recipients are the people you alert: emergency contacts stored (encrypted) in your team. They receive SMS, email, voice, or push notifications and acknowledge via a public link. Recipients never need an account and are always free, on every plan.
A small security team can therefore protect a much larger group: two responder seats can alert an entire office.
Free-tier limits
The Free plan includes 1 team with up to 5 members and 2 responder seats, plus 3 encrypted contacts, 10 encrypted secrets, and 100 emergency messages per month. Paid plans lift these limits — see Billing and plans.
Roles
Organization members hold one of: owner, admin, billing admin, or member. Within a team, roles are admin, member, or viewer — team admins manage membership and settings; members can do day-to-day work like sending messages and managing documents; viewers are read-only.
Invite a teammate
- Open your team and choose Invite member.
- Enter their email and pick a team role. The invitation is delivered by email with an expiring link.
- The invitee creates an account (or signs in) and accepts. Accepting adds them to the team and to the organization that owns it, so entitlements and billing resolve correctly.
- On paid plans, the billed responder-seat count follows your active organization membership automatically.
After they join: grant encryption access
New members generate their own encryption keys at first login, but they can't read the team's encrypted contacts or hold secret shares until an existing key-holder grants them access. Glassbreak shows key-holders a banner ("N teammates can't see contacts") with a one-click grant; the grant re-encrypts the team key for the new member in the granter's browser, so the server never sees it. If a teammate reports they can't see contacts, that grant is almost always the missing step.
The same logic applies in reverse: removing someone from a team does not retroactively un-know what they knew, so for secrets Glassbreak supports re-keying — see the deletion and re-share notes in the secrets guide.