Workspace name and region
The workspace's name, id, creation date and data region, and who is allowed to rename it.
Settings then Organization is the workspace itself: what it is called, the id we ask for when you contact us, when it started, and where its encryption key is held. Reading the page needs org:read.
What it holds
| Field | What it is |
|---|---|
| Name | The label shown across the console. The only field anybody can change here |
| Organization ID | The workspace id. Quote it when you contact us |
| Created | The day the workspace started |
| Billing | Either a payment method is on file, or the line says you are not billed on the Free plan. Which processor holds it and its customer reference never appear |
| Data Region | Where your encryption key is held |
Renaming
Renaming needs org:update, which Owner and Admin carry. Somebody without it sees the name as plain text and a line saying only admins can change it.
Only the label moves. The workspace id stays where it was, so every project, value, role assignment and entry in the record is where it was too. Renaming to the name it already has changes nothing and files nothing.
What each action needs
| Action | Needs | Confirm it is you | Recorded as |
|---|---|---|---|
| Open the page | org:read | No | not recorded |
| Rename the workspace | org:update | No | org.renamed |
| A rename somebody was refused | attempted without org:update | No | org.renamed with a denied result |
A refusal is recorded the same way a success is, with the result telling the two apart. Somebody trying to rename a workspace they may not rename is worth being able to see.
Canceling the plan and deleting the workspace live on Danger Zone.
Next: members and invites.