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. Below them sit Members, to give someone a different role in this project than in the organization, Shared configuration, and Portability, which exports the whole project as plain Kubernetes manifests.
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. It only appears when you belong to another organization, and you need to be an admin there too.
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 |
|---|---|
| Settings | The organization's display name, which only an owner changes, and Delete organization, once no projects are left |
| Members, Domains, API tokens, Notifications, Registries | Their own rows in the organization's sidebar. See Members and roles, Pull credentials and Alerts |
How much CPU, memory and disk each project may reserve comes from your plan and is shown on the Plan page. There is nothing to set per project; a bigger plan raises it for every project.
Limits and gotchas
- Names are permanent, display names are not. Anything a URL, a label or another workload references cannot be renamed.
- 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.
- Everyone can read these pages, only admins change them. A member can deploy everything in a project and cannot rename it; only an owner renames the organization.
Related
- Organizations, projects, workloads for what each level owns.
- Plans and costs for the capacity each plan gives a project.
- Members and roles for who may open these pages.