Workspace name and region
The workspace's name, id, creation date, plan and key region, and who is allowed to rename it.
Path: Settings > Organization
Fields
| Field | Content |
|---|---|
| Name | The label shown across the console. The only field you can edit |
| Organization ID | Your workspace id. Quote it when you contact us |
| Created | Your workspace creation date |
| Plan | Your plan, linking to Billing, and what it bills: per human seat, or the seat cap on Free. Machine identities are free on every plan |
| Key region | The AWS region of our platform key. A customer-managed key keeps its own region: see Encryption and BYOK |
Rename
Type the new name and select Rename. The button stays disabled until the name differs from the current one. You need org:update (held by Owner and Admin); without it, the field is read-only and the note under it names the permission.
Only the label changes. Your workspace id stays the same, so projects, values, role assignments, and audit entries are unaffected. Renaming to the current name is a no-op; we write no audit entry.
Required permissions
Full matrix: Roles and permissions.
| Action | Permission | Step-up | Audit entry |
|---|---|---|---|
| Open the page | org:read | No | none |
| Rename the workspace | org:update | No | org.renamed |
| Rename attempt we refuse | attempted without org:update | No | org.renamed with a denied result |
Elsewhere in Settings at the bottom links Members (with member:read), Security, and Danger Zone.
Plan cancellation and workspace deletion: Danger Zone.
Next: Members and invites.