Using the web app

Everything you can do from the browser, without touching the CLI.

Dashboard

Lists every project you can access across every organization you belong to (see Teams & sharing below) — your own, plus any a teammate has shared with you. An organization filter next to the search box narrows the list down to one org at a time; it only appears once you're in more than one. From here you can:

create a new project (a dev environment is added automatically);
open a project to manage its environments;
rename or delete a project — deleting a project deletes all of its environments, variables, and version history, with no undo.

Environments

Inside a project you'll see its environments (e.g. dev, staging, prod). Create as many as you need — names must be unique within a project. Open an environment to manage its variables.

The variable editor

Masked by default — values are hidden until you click the reveal toggle for a row.
Per-row copy — copy a single value without revealing it on screen for long.
Copy all as .env — copies the whole environment, formatted as a .env file, to your clipboard.
Paste .env — paste a whole file's contents to bulk add/update keys in one go (an upsert-merge: keys not present in the pasted text are left untouched).
Add / edit / delete a single key at a time.
Multiline values — fields auto-grow and support multi-line values (e.g. PEM-formatted keys); revealed values wrap instead of overflowing.

Deleting an entire environment or project has no undo. A deleted variable, though, can be brought back by rolling the environment back to an earlier version — see Version history below.

Version history & rollback

Every change to an environment — an edit in the table, a Paste .env import, or a CLI push — creates a new numbered version. Click the History button on an environment to see every version with who made it and when, and to restore any earlier version. Restoring creates a new version rather than erasing what came after (like git revert, not git reset), so a restore can itself always be undone.

Every account gets a personal organization automatically. Create or join a team organization from Teamsin the sidebar — invitations, pending status, member roles, and removal are handled entirely by Clerk's own organization UI there. When you belong to more than one org, a picker on that page lets you switch which one you're managing.

Manage access— from a project's menu, grant an org member or a group one of three roles: Viewer (read-only), Editor (can edit variables and environments), or Admin (can also manage access and delete the project). Org admins/owners always have admin access to every project in the org, without needing an explicit grant.
Groups (Settings → Groups, org admins only) — create named groups of org members and grant a group access to a project in one step instead of adding people one at a time.

Access control is currently project-wide — a role applies to every environment in the project. Restricting a role to specific environments (e.g. Editor on dev but Viewer on prod) isn't enforced yet.

CLI tokens (Settings → CLI Tokens)

Personal access tokens authenticate the envhq CLI (mainly for CI/headless use — interactive envhq loginuses a browser flow instead and doesn't need one of these). From this page you can:

create a token — the plaintext value is shown once, at creation time only; copy it immediately;
see each token's name and last-used time (never the token itself again);
revoke a token instantly if it's no longer needed or may have leaked.

Theme

Toggle light/dark mode from the header. The app defaults to light mode; your choice is remembered on the device.