Organizations & members
How StackRadar organizations work: the roles and what each allows, inviting teammates by email, accepting an invite, and removing members.
One organization owns everything
Everything in StackRadar belongs to an organization: every cluster, every cluster's API key, every SBOM and finding those clusters report, and the plan that sets your limits and history window. Members come and go; the organization keeps the data. That is deliberate — removing the person who created a cluster changes nothing about the cluster, so offboarding a teammate is never a data question.
You can be a member of more than one organization, and the dashboard always operates on one active organization at a time.
Roles
Three roles exist: owner, admin, and member.
| Role | What it allows |
|---|---|
| Member | The whole security surface, read-only: clusters, workloads, SBOMs, vulnerabilities, and usage. Connecting, renaming, or deleting clusters, rotating API keys, and organization management all require admin or owner. |
| Admin | Everything a member can do, plus cluster management (connect, rename, delete, rotate API keys), organization settings (name, color), inviting and removing members, managing pending invites, and the plan & billing. |
| Owner | Everything an admin can do, plus promoting members to admin and deleting the organization. |
Each organization has exactly one owner — the person who created it. The owner's role can't be changed, and the owner can't be removed or leave; the only exit is deleting the organization. Admins can demote other admins to member and remove them, but only the owner can promote a member to admin — otherwise any admin could mint peers, and the owner would have no say in who manages the organization.
Inviting a teammate
Invites are by email, and require the admin or owner role:
- In the dashboard, open Organization Settings → Members and click Invite Member (the same button exists on the Invites tab).
- Enter the email address and pick a role — Member or Admin. There is no way to invite an owner.
- The invitee receives an email — "name invited you to join organization on StackRadar" — with an Accept invitation link and the expiry date. Every invite expires after 7 days.
The invite is valid the moment it's created, whether or not the email arrives: the link itself is the credential, and you can copy it from the Invites tab and hand it over on Slack if the email lands in spam.
Three rules keep the invite list honest:
- Pending invites count toward your plan's member limit. Otherwise you could send ten invites while one seat is free and have all ten accepted.
- You can't invite someone who is already a member.
- One active invite per email address — cancel the old one to change its role.
What the invitee sees
The link opens app.stackradar.io/invite/<token>, which shows the organization name and the role being offered.
- No StackRadar account yet — they sign in with GitHub or Google straight from the invite page, which creates the account, and land back on the invite. No personal organization is created for them; accepting puts them directly into yours.
- Existing account — they sign in (or already are), and click Accept invite. The organization they joined becomes their active one.
The link is the credential, not the email address: whichever account presents the link is the one that joins, because an invite sent to a work address is routinely opened from a GitHub account registered under a personal one. When the two differ, the page says which account will join before the invitee accepts. Accepting also counts as agreeing to the Terms of Service — the page says so next to the button.
Managing pending invites
Organization Settings → Invites (visible to admins and the owner) lists every outstanding invite: email, role, who sent it, and when it expires. Two actions per row:
- Copy link — the same link the email carried. This is also how you resend an invite: there's no separate resend action, because the link hasn't changed and sending a second email would just race the first.
- Cancel — revokes the invite immediately. The link stops working the moment you cancel; someone holding the email can no longer join.
An expired invite can't be revived — create a new one, which generates a fresh link.
Changing roles and removing members
On Organization Settings → Members, admins and the owner get a role selector and a remove button on every row except the owner's and their own. Role changes and removals take effect immediately.
Removing a member revokes their access and nothing else. Clusters, API keys, SBOMs, and findings all belong to the organization, not to the person who created them — so offboarding never orphans data. A member can also leave an organization themselves; the owner is the one exception.
Ownership
Ownership transfer is not currently supported. If you need to hand an organization to someone else, email contact@stackradar.io and we'll sort it out.
Next steps
- API keys & cluster scopingHow StackRadar API keys work: one cluster-scoped key per cluster, why every scanner request requires one, and how to get and rotate keys safely.
- Plans, retention & deletionWhat each StackRadar plan’s history window keeps, what happens when you downgrade or cancel, and how to delete clusters, organizations, and all stored data.