Docs
Getting Started
Everything you need to go from a fresh account to your first CLI pull.
1. Create an account
Sign in with Google — that's the only sign-in method, by design. Google verifies you actually own the email address, so EnvSync never has to store or verify a password itself. Your account is created automatically on first sign-in. There's nothing to install for the web app — it runs entirely in the browser.
2. Create an organization
Organizations are the top-level container for your team. The account that creates one automatically becomes its Owner. You can belong to and switch between multiple organizations from the switcher in the top navigation bar.
3. Create a project
Projects group related environments together — typically one project per application or service.
4. Add an environment
Every project can have up to four environment tiers: Development, Testing, Staging, and Production. Each tier has its own secrets and its own access rules — see Roles & Permissions.
5. Add a secret
Add a key/value pair from the environment page. Values are encrypted before they ever hit the database — see Security & Encryption for exactly how.
6. Install the CLI
npm install -g @ashishlekhyani/envsync-cli7. Log in and pull
Generate a service token from Settings → CLI & Tokens, then:
envsync login <your-token>envsyncRunning envsync with no arguments launches an interactive menu that picks your project, environment, and action (like pulling into a real .env file) for you — no IDs or flags needed. See the full CLI Reference for every command.
8. Invite your team
From Team → Invites, generate a shareable invite link. Only the Owner or a project's own Admin can send an Admin/Developer/Viewer invite — it requires picking the project that role applies to, since those roles are project-scoped. Any member can send a plain org-only invite (no project, no role). See Roles & Permissions for the full model. Anyone can leave an organization or a project on their own from Settings, no admin required.