Projects and ownership
Organize workload resources, teams, region access, and project deletion.
Projects isolate application resources, permissions, quotas, and usage within an organization. A project can use shared fleet capacity without owning its nodes.
Create a project
You have the Organization Admin role. Open Organization → Projects → Create project, enter a name, assign an owner team, and select permitted regions and node pools. The project receives an immutable ID used by resource references and automation.
Set quotas and default operational policies before granting broad operator access. A project without its own budget still contributes usage to the organization account.
Membership and ownership
Use team bindings to assign Project Viewer, Project Operator, or a custom role. The owning team is the operational contact; ownership alone does not override explicit permission checks. Review inherited organization access in the effective permissions view.
Resources created through a service account belong to the selected project, not to the person who created the service account. Removing a member does not delete that member's resources.
Defaults
A project can define default labels, a backup policy, firewall policy, and allowed image sources. Defaults populate new-resource requests or apply through policy selection. They do not rewrite existing guests unless a documented policy operation explicitly selects those resources.
Changing a default network does not move current interfaces. Changing a default backup selector can change future backup coverage; preview the selected set before saving it.
Resource transfers
A resource's project is an ownership boundary. Directly changing project_id
in a resource update is unsupported. Use the dependency-bundle transfer workflow, or restore into the destination project and update dependencies.
A transfer checks network references, credentials, quota, and destination access. Related resources must be transferred together or replaced with valid references. An isolated volume cannot retain an attachment to a droplet in another project.
Suspend creation
Project admission can be disabled to prevent new resources while retaining existing operation and read access. This is useful during decommissioning or policy review. It does not stop guests, pause billing, or expire backups.
Delete a project
Open Project settings → Delete project and review its inventory. Deletion is blocked while application resources, retained backups, active operations, or retention-locked records require the project.
Remove workloads and network dependencies, release addresses, revoke service accounts, and address retained data according to policy. Organization fleet nodes are not project resources and remain registered.
Deletion removes the live project scope. Audit and operation history can retain its ID under organization retention. Export required records before removal and verify usage after cleanup in Usage and billing.