Create a Project from UI

Follow these steps to create a Project using the Axio web interface.

Prerequisite

Ensure that you have permission to create Projects in your Organization before creating a Project.

Who can create projects:

Owner and Admin — can always create projects (when the Create Project action is available).
Member — can create projects when granted organization-wide access. Members with project-, workspace-, or environment-scoped access only cannot create new projects.
Viewer and Unassigned — cannot create projects.

If you lack permission, the Create Project button is disabled and a tooltip explains why. Contact an organization Owner or Admin to assign the appropriate role via Administration → Roles & Access.

Step-by-Step Guide

Sign in to Axio

Sign in to the Axio platform using your email and password, plus your Organization ID — an 8-character code shown on Organization → Overview. Use the Organization ID at sign-in, not the organization display name or slug.

Go to Projects

Navigate to:

Organization → Projects

If no projects exist yet, you can also click Create Your First Project from the empty state on the same page.

Click Create Project

Click the Create Project button on the Projects page toolbar (or Create Your First Project when the list is empty).

Fill in Project Details

Provide the following information in the Create Project dialog:

Name (required) — A unique display name for the project within your organization. Axio auto-generates an internal slug from the name. Names are compared case-insensitively (ecommerce and Ecommerce cannot both exist).
Description (optional) — A short summary of the project's purpose.

Review and Confirm

Review the entered information and click Create to save the project. Click Cancel or the back arrow to close the dialog without saving — no changes are made.

While the project is being created, the button shows Saving…. If the name already exists or validation fails, an error message appears in the dialog.

Project Created

On success, the dialog closes and the new project appears in the Organization → Projects list. You are automatically granted access to the project you created.

The project is now ready to contain Workspaces. Environments are created within workspaces, not directly on the project.

Create Project

Name * Description

Field reference

Field	Required	Rules
Name	Yes	Must not be empty. Must be unique within the organization (case-insensitive). A URL-safe slug is generated automatically.
Description	No	Free text. Shown on the Projects list and project detail page.
Sensitive	No	Defaults to off. When enabled, restricts delete, archive, and destroy operations — see below. Requires permission to update the project to change later.

What Happens Next?

After creating the Project:

The Project becomes available under Organization → Projects and on the project detail page.
You can add one or more Workspaces to the Project.
Workspaces can contain Environments.
You can mark the Project as Sensitive during creation or when editing the project.
You can archive the Project when it is no longer required (see below).
To change the name, description, or sensitive flag later, open the project row actions and choose Edit, or edit from the project detail page.

Make a Project Sensitive

A Project can be marked as Sensitive when creating it or when editing it later. Use this for production-critical or compliance-bound projects that must not be accidentally removed or destroyed.

Sensitive Projects cannot be deleted
Sensitive Projects cannot be archived
Destroy deployments for linked stacks are blocked
Infrastructure managed through linked stacks cannot be torn down via destroy deployments while the project remains sensitive

Who can change it: Users with permission to update projects (typically Owner, Admin, or an authorized Member).

Archive a Project

Archive a Project when it is no longer actively required. Archiving is a soft deactivation — the project is retained for reference but treated as inactive.

Behavior

Archived Projects are retained for reference and can be unarchived later
Archived Projects are not available for ongoing operations
Sensitive Projects cannot be archived
System and Git-managed projects (including the auto-provisioned Default Project) cannot be archived from the UI

Archive vs delete

Archive — Reversible; project data is kept; workspaces may remain attached
Delete — Permanent; requires typed confirmation; the project must contain no workspaces and must not be sensitive

How to archive: On Organization → Projects, open the row actions menu for the project and choose Archive. To restore, choose Unarchive on an archived project.

Default project and unassigning workspaces

Every organization is provisioned with a system Default Project (with a Default Workspace and Default Environment). This resource cannot be archived or deleted from the UI.

A Workspace can be unassigned from its current Project. When unassigned, the workspace and any environments inside it are moved to the Default Project. Git-managed and system workspaces cannot be unassigned.