Skip to main content
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

The role gates the Cloud API (orgs, members, billing). Inside a connected cluster, K8s RBAC takes over - see Cloud RBAC for how cloud:owner / cloud:member / cloud:viewer are mapped to ClusterRoles by Radar’s chart.

​
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.
Organizational metadata you might also need lives elsewhere:

​
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. This:
  1. Disconnects every cluster (the in-cluster Radar pods survive but stop reaching the control plane - uninstall the chart to fully clean up).
  2. Cancels the Stripe subscription (no further invoices).
  3. Drops members from this org (their accounts are not deleted - they just lose membership).
  4. Schedules audit log deletion per the org’s retention floor.
There’s no recovery once delete is confirmed.

​
See also