Blastoff Team Workspaces
A Blastoff workspace gives a team shared reports, tags, screenshots, MFA configurations, hosted inboxes, API keys, and audit history.
Capacity
A workspace includes:
- 5 seats
- 20,000 report uploads per billing cycle
- 25 pooled MFA configurations
- 25 pooled hosted inboxes
- 1,000 retained messages per inbox for 30 days
Additional seats are $30 USD per month. Increases are prorated; reductions begin with the next billing period. See Pricing for current terms.
Roles
| Role | Capabilities |
|---|---|
| Owner | Manage members, ownership, billing contact, subscription, seats, and workspace access |
| Admin | Invite and manage members, manage workspace resources, and revoke member credentials |
| Member | Use shared workspace resources and contribute mission results |
Only an Owner can change ownership, manage billing, or purchase seats. A workspace must always retain at least one Owner.
Invite teammates
- Select the Blastoff workspace in Mission Control.
- Open Workspace.
- Enter the teammate's email address.
- Choose Member or Admin.
- Send the invitation.
Invitations expire after seven days. Pending invitations occupy seats. A user can belong to only one Blastoff workspace at a time.
Manage seats
Five seats are included. Owners can increase capacity immediately. A seat decrease:
- cannot reduce capacity below currently occupied seats
- begins at the next billing period
- should be preceded by removing members or revoking pending invitations when necessary
Shared versus personal scope
Use the workspace selector to switch between Personal and Blastoff resources. Reports and hosted utilities remain in the scope to which they were created or uploaded.
For CLI uploads, the selected destination comes from the API key used by testronaut login; it does not automatically follow the workspace currently selected in the browser.
Credentials and offboarding
Admins and Owners can revoke a member's workspace API keys and active sessions. Removing a member also revokes their workspace credentials.
Workspace API keys are bound to both their creator and the workspace. Each teammate should create their own key rather than sharing one.
Audit history
Mission Control records recent administrative activity such as invitations, role changes, credential revocations, membership removal, API-key actions, and seat changes.