Ratify tenant grouping identifiers
This commit is contained in:
parent
11a14648c4
commit
c3800b6dea
1 changed files with 8 additions and 4 deletions
|
|
@ -216,12 +216,16 @@ Suggested identifiers:
|
||||||
```text
|
```text
|
||||||
tenant:platform
|
tenant:platform
|
||||||
tenant:coulomb
|
tenant:coulomb
|
||||||
tenant:sandbox:<name>
|
tenant:<grouping>:<name>
|
||||||
tenant:customer:<name>
|
|
||||||
```
|
```
|
||||||
|
|
||||||
`tenant:platform` is the platform control-plane tenant. Tenant
|
`tenant:platform` is the platform control-plane tenant and `tenant:coulomb`
|
||||||
administration for `tenant:coulomb` or later tenants must never imply
|
is the reserved internal/reference tenant. Both are intentionally ungrouped
|
||||||
|
special cases. External-shaped tenants use a grouping orthogonal to their
|
||||||
|
capability roles: `trial`, `friendly`, `single`, `small`, `medium`, `large`,
|
||||||
|
`enterprise`, `consumer`, `family`, `community`, `association`, or `agentic`.
|
||||||
|
For example, Binky Hedgehog GmbH is `tenant:friendly:binky`. Tenant
|
||||||
|
administration for `tenant:coulomb` or any grouped tenant must never imply
|
||||||
platform-root authority.
|
platform-root authority.
|
||||||
|
|
||||||
Subjects may have access to multiple tenants, but a token used for a
|
Subjects may have access to multiple tenants, but a token used for a
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue