An Org serves as a tightly isolated bounded context that encompasses all the resources managed by Control Plane. These resources comprise domains, images, workloads, GVCs, users, groups, service accounts, and more.
It's possible for a physical organization, to create multiple 'orgs,' although this is not mandatory. Creating multiple orgs can be beneficial in order to establish complete isolation between environments, for instance.
Refer to the Create an Org guide.
A user can be a member of one or more Orgs.
>
to the right of the current org.Yes
.Control Plane offers the ability to ship all Org logs to an external provider.
Please click here for additional details and configuration instructions.
The console UI will automatically sign out if inactive for 15 minutes. This timeout duration is the default setting (for PCI compliance) and can be modified.
This timeout setting (in seconds) can be adjusted from the Info
page when clicking on the Org
link from the left menu.
The permissions below are used to define policies together with one or more of the four principal types:
Permission | Description | Implies |
---|---|---|
edit | Modify org | view |
grafanaAdmin | Grantees are made Admin in Grafana, otherwise the role 'Viewer' is assigned | |
manage | Full access | edit, grafanaAdmin, manage, readLogs, readMetrics, readUsage, view, viewAccessReport |
readLogs | Grantees can read logs from all workloads | view |
readMetrics | Grantees can access usage and performance metrics | |
readUsage | Grantees can access usage and billing metrics | |
view | Read-only view: every org member can view their org | |
viewAccessReport | Grantees can inspect the granted access report on all resources within the org |
Displays the permissions granted to principals for the Org.
To view the CLI documentation for an Org, click here