Dashboard Guide

Projects

A project is the unit of isolation for variables and environments. Each project belongs to one organization and can have its own team members, API keys, and per-environment configuration.

Creating a Project

Open Projects from the sidebar.
Click New Project in the top-right.
Enter a name and optional description. Names are unique within an organization.
Click Create. You'll land on the project detail page with three default environments pre-provisioned: development, staging, production.

Role gating: only Owners and Admins see the New Project button. Members and Viewers can use existing projects but cannot create new ones.

Plan gating: the free plan caps the number of projects per organization. Upgrade at /dashboard/billing.

Project List

The project list supports:

Search by name (free-text filter, debounced).
Pagination for large orgs.
Per-card metrics: variable count and member count at a glance.

Project Detail Page

Click a project from the list to open its detail page. You'll see:

An environment tab strip (development / staging / production / custom). Click to switch.
The variable list for the selected environment.
Total keys and member count in the header.
A toolbar with Add Variable, Bulk Upload, and Download .env actions.

Editing Project Metadata

From the project detail page, click Settings (gear icon) to rename the project or update its description. Names cannot collide with another project in the same org.

Deleting a Project

Delete a project from Settings → Danger Zone. The dialog requires you to type the project name to confirm.

Deleting a project is irreversible. All variables across all environments are removed. API keys scoped only to the deleted project are auto-revoked.

Bulk Operations

Download .env exports all variables of the active environment as a .env file.

Bulk Upload accepts a .env file and creates / overwrites variables in one transaction.

For org-wide secrets (used across all projects), see /dashboard/secrets.

Per-Project Access

Org members inherit access to all projects by default; finer per-project access is governed via API key project scopes (API Keys) and roles (Access Control).