Organizations & roles

In Radar Cloud, the organization is the tenant boundary. Clusters belong to one org. Members belong to one or more orgs. Billing, audit log, SSO config, and notification destinations are all org-scoped.

​

Roles

These roles control what someone can do in Radar. Access inside Kubernetes is configured separately for each connected cluster and can also use identity-provider groups. See RBAC under Cloud mode for details.

​

Multi-org membership

A user can belong to multiple orgs (e.g. one org per company they consult for, or a personal org plus a work org). The org switcher is the dropdown at the top of the left rail. Switching orgs reloads the page - your “current org” is server-side state, so links to clusters / settings always resolve in the correct tenant.

​

Org settings

Settings → Organization (owner-only edit; members see read-only):

• Name - human label.
• Allowed email domains - list of domains that auto-join. Free-mail providers (gmail.com, etc.) are blocklisted.
• Default invite role - the role applied when users join via auto-join or an invitation link without a pre-selected role: member or viewer. It can’t be owner, because it also applies to anyone who joins through SSO or domain auto-join.

Organizational metadata you might also need lives elsewhere:

• Members - Members & invitations
• Billing - Billing & plans
• SSO - SSO
• Audit log - Audit log
• Notifications - Notifications

​

Creating a new org

From the org switcher, click Create organization. Name it, and you’ll land on its empty home page. Connecting your first cluster mints the org’s first audit event.

​

Deleting an org

Owner-only. Settings → Organization → Delete organization. If the org has an active, trialing or past-due subscription, the delete is refused. Cancel the subscription first from Settings → Billing → Manage billing, then come back. Deleting the org:

1. Removes every cluster and closes its tunnel. The in-cluster Radar pods keep running but can no longer reach the control plane, so uninstall the chart to clean up fully.
2. Drops all members from this org. Their user accounts aren’t deleted, they just lose membership.
3. Deletes the org’s audit log immediately. Nothing is kept for the retention window, so export it as CSV first if you need a record.

There’s no recovery once delete is confirmed.

​

See also

• Members & invitations - how to add people.
• SSO - SAML / OIDC.
• Billing & plans - free tier and Team / Enterprise / Custom.
• Cloud RBAC - how the role flows into K8s.