Skip to main content
Updated May 8, 2026 A project is a container for resources — VMs, VPCs, public IPs, Object Storage buckets, snapshots, backups. Resources never live “in the account” directly; they always belong to one project. Projects are also the unit of access control — a member with a Project Member role on customer1 only sees customer1’s resources. Every account starts with a Default project, pre-created at signup, and you can never delete it. Most accounts that don’t need access partitioning leave it as their only project. Create more projects when you want to isolate customers, separate environments (prod / staging), give per-team scoping, or break out billing entities.

Open the Projects tab

In Team & Projects, switch to the Projects tab.
Team & Projects Projects tab showing the heading "Organize resources with projects for better access control", a + Create Project button on the right, and two project rows: Default (Default badge, 0 members, created 1/22/2026) and customer1 (1 member, created 3/23/2026)
The list shows every project in your account with three columns: Click the orange + Create Project button on the right.

The Create New Project dialog

Create New Project dialog with subtitle "Create a project to organize your resources and manage access.", a Name field with placeholder "e.g., Production", a Description (Optional) textarea with placeholder "What is this project for?", and Cancel / Create Project buttons
The dialog is intentionally short — two fields and a save button.

1. Name

Pick a label that’s easy to recognize when assigning resources or members later. Common patterns: Names must be unique inside your account. Names can be renamed later via the row’s Edit Project — see Edit or delete a project for the rename flow.

2. Description (optional)

Free-form. Useful for telling teammates what this project is for — “Production workloads for ACME Corp’s whitelabel deployment”, “Internal staging — destroy and rebuild freely”. Shows up in the project’s row when expanded. Skip if you don’t need it. The field has no length cap; use as much detail as helps the team.

3. Click Create Project

The project is created in seconds and appears in the Projects list. The new row shows:
  • The display name with no Default badge
  • 0 under Members (no one assigned yet)
  • Today’s date under Created
The new project is empty and immediately usable. From this point on:
  • The new project appears in the top-bar project picker for anyone with access to it
  • You can add members to it from Team & Projects → Members → row's expansion → + Add to Project, or by inviting a new member with the Project access level scoped to this project
  • Anyone working in the project switches to it via the top-bar project picker, then creates VMs / VPCs / IPs / buckets the normal way — they all land in this project automatically

What you cannot do

Who can create projects

A member needs the account.projects.create permission to use the + Create Project button. The Owner has it; the Admin account role has it; Billing and Member account roles do not. Project-only members never see the Projects tab at all. If the button is greyed out or missing, you don’t have the permission — ask the Owner or an Admin to either create the project or grant you the permission via a Custom role.

Edit or delete a project

Rename, change description, or delete a project.

Invite a member

Add a member scoped to a specific project.

Projects and scoping

How project scope affects every resource and API call.
Last modified on May 8, 2026