Dashboard Guide
Environments
Environments isolate variables across the project lifecycle. EnvVault provisions three by default — development, staging, production — and lets you add arbitrary custom environments such as qa, uat, or per-PR previews.
Selecting an Environment
Open any project. The environment tab strip at the top of the page lets you switch between environments. The variable list and all toolbar actions operate on the selected environment.
Adding a Custom Environment
- From the project detail page, click + Environment at the end of the tab strip.
- Enter a name (e.g.
qa,pr-1234). Names are unique within the project. - The new environment opens with an empty variable list.
envv env set FEATURE_NEW_NAV true -e qa.Adding Variables
- Pick the target environment.
- Click Add Variable.
- Provide a key (auto-uppercased, allowed chars
A-Z 0-9 _ - .) and a value. - Save. The variable appears in the list immediately.
The same key can hold different values across environments — e.g. DATABASE_URL per-environment.
Bulk Upload from .env
Click Bulk Upload. Drop a .env file or paste contents. Two modes:
Single environment
Uploads all keys to the currently selected environment.
Multi-environment
Drop several files at once, each targeting a named environment.
Existing keys are overwritten. Lines starting with # are treated as comments.
Downloading a .env File
Click Download to export the active environment as a .env file. Useful for one-off local boots or for diffing two environments.
.env files as sensitive. Don't commit them; consider deleting them after use.Deleting an Environment
Custom environments can be removed via the trash icon next to the tab. The three default environments (development, staging, production) cannot be deleted.
Project vs Org-Wide Scope
Variables on this page are project-scoped. For values that should be the same across every project in the org (e.g. a single Stripe key), use Organization Secrets instead. The CLI merges both at runtime.