guides
Organizations & teams
An organization is a self-contained account: its own assets, findings, team, and billing. Each org is fully isolated from every other. This page covers creating orgs, roles, and inviting teammates.
what you'll learn
- How organizations work and how to switch between them
- How to create a new organization
- What each role can do
- How to invite teammates and how they accept
Organizations
An organization owns its assets, findings, team, and subscription. A user can belong to several. Use the org switcher in the header to move between them — it lists your organizations with the active one checked, and remembers your selection. There is no cross-organization view; you always work inside one org at a time.
Creating an organization
- 1
Open the new-org form
In the header org switcher, click + New organization (or open
/orgsand use Add organization). - 2
Fill in the details
Organization name is required (e.g.
Acme Protocol); contact name, contact email, and notes are optional. Click Create organization. - 3
Set it up
You're taken straight into onboarding to connect your first asset. See Getting started.
Roles
Roles are scoped to each organization — your role in one org says nothing about another.
| parameter | type | description |
|---|---|---|
owner | role | Full control, including billing and deleting the org. Every org has at least one owner. |
admin | role | Manage members, billing, settings, and scans. |
member | role | Connect assets, run scans, and triage findings. |
viewer | role | Read-only access. |
Inviting teammates
- 1
Open team members
Go to the org's Settings and find the team members section (owners and admins only).
- 2
Invite by email
Enter the person's email in invite by email, choose a role, and click Send invite. This creates a pending invitation that expires in 14 days.
- 3
Share the invite link
Muster shows the invite link with a copy button — email delivery is coming soon, so for now you share the link yourself (Slack, email, wherever). Every pending invite in the list has its own copy link and revoke buttons.
Accepting an invite
The link opens /invite/<token>, showing “Join {org} as {role}”. The invitee signs in — or creates an account with the invited email address — and accepts, joining the org with the role you chose. Invitations are scoped to that single organization and never expose any other org's data.
Isolation
Access is strictly by membership. You can only ever see organizations you belong to, and API keys are scoped to one org. Muster staff can see platform health, but not your findings.
continue