How to securely share .env files with a team

The safe way to share .env configuration is to share access to an encrypted environment — not to transmit the file itself.

Replace the zip-file ritual

New hires should not receive last quarter’s secrets.zip. Invite them to the organization, assign a role, and let them pull the environment with the CLI.

Recommended workflow

Owner imports the existing .env once. Teammates run eanvi login, eanvi init, and eanvi pull. Updates happen in the vault; everyone pulls again.

Revoke access by removing membership — no chasing old files
Production roles stay tighter than development
Audit logs show who revealed values

eanvi login
eanvi init
eanvi pull

Related resources

.env management
Team secrets
Team docs

Try EANVI

Create a workspace, import a .env, and pull secrets from the CLI.

Start free Read the docs