Use cases / Sharing .env secrets with a team
Share .env secrets with your team — without Slack or a password manager
Updated September 26, 2026
Stop pasting .env files into chat. Import yours once, grant each teammate access to the project, and everyone pulls or runs with the same encrypted secrets.
Most teams share secrets the same way: someone pastes a .env into a DM. The values then live forever in chat history, nobody knows who has which version, and rotating a key means another round of pasting.
Import the file you already have
bippass push encrypts a local .env on your machine and uploads the ciphertext to the active project and environment.
$ bippass push $ bippass push --file .env.production --env production
Grant access per project
Adding someone to a workspace lets them see it exists; it does not let them read anything. bippass grant wraps the project key to that person’s own public key, which is what lets them decrypt.
$ bippass grant --email dev@acme.comEveryone gets the same values
Teammates run the app with bippass run, or pull a .env if a tool insists on one. bippass diff shows how a local file differs from the project, and bippass sync merges the two, asking about conflicts.
$ bippass run -- npm run dev $ bippass diff $ bippass sync
Every value is encrypted before it leaves a laptop. BipPass stores ciphertext it has no key for — including when you share it.