Project and organization settings
The two settings pages, what each one changes, and the three actions there is no undo for.
Where each lives
Settings sit at the level they affect. A project's settings change that project; an organization's settings change every project below it.
Most day-to-day configuration is not here at all: it belongs to the workload it affects. Domains are on the app, backups are on the project's Backups page, and secrets are in Configuration. Settings is for the things that describe the container rather than its contents.
Project settings
Its display name and description, which are cosmetic and safe to change at any time. The project's own name is not editable, because other things reference it.
Two actions here have consequences:
Transfer to another organization. The project moves with its workloads, and the plan, billing and members of the destination take over. Useful when a project outgrows the organization it was started in.
Delete the project. Everything inside goes: apps, databases, volumes, and the recovery points. The dialog asks you to type the project name, because there is nothing behind it.
Deleting a project deletes its recovery points too, so a backup does not save you from this. If you might want any of it later, restore or export first.
Organization settings
| Section | What it sets |
|---|---|
| Details | The organization's display name |
| Quota defaults | How much CPU, memory and disk a new project gets, inside the plan's ceiling |
| Registries | Pull credentials and the build registry. See Pull credentials |
| Notifications | The channels alerts are delivered to. See Alerts |
Quota defaults are the one worth understanding. They apply to projects created afterwards, not retroactively, so raising them does not widen an existing project. That one you change on the project itself.
Limits and gotchas
- Names are permanent, display names are not. Anything a URL, a label or another workload references cannot be renamed.
- Quota defaults are not retroactive. A new default is for new projects.
- A transfer changes who pays. The destination organization's plan and limits apply immediately, so a project moving into a smaller plan may be over its limits and unable to create anything new.
- Only admins see these pages. An editor can deploy everything in a project and cannot rename it.
Related
- Organizations, projects, workloads for what each level owns.
- Plans and costs for the ceiling quota defaults sit inside.
- Members and roles for who may open these pages.