Team Workflows

Team Workflows

Owner: set up the project

The person creating the project runs init once in the repo folder:

storemyapi init

This creates the project in the cloud and writes .storemyapi.json locally. Push existing secrets to the cloud:

storemyapi push

Owner: invite teammates

storemyapi share add alice@company.com read
storemyapi share add bob@company.com write

• read: can pull keys and run env run
• write: can also push and set/delete keys

Check who has access at any time:

storemyapi share list

Remove access when someone leaves:

storemyapi share remove alice@company.com

Teammate: accept and set up

When a new developer joins, they:

# 1. Install and authenticate
npm install -g storemyapi
storemyapi login

# 2. Accept the pending invite
storemyapi share invites   # interactive dropdown, accept or decline

# 3. Link their local folder to the project
storemyapi link            # choose from dropdown

# 4. Pull the keys
storemyapi pull            # writes to .env

# 5. Start working
npm run dev

Or skip the local .env entirely:

storemyapi env run -- npm run dev

No more sharing secrets over Slack

Every developer has their own storemyapi account. No shared passwords, no pasted keys in chat. Access is granted and revoked per-person from the CLI or web dashboard.

Reviewing access

The web dashboard at storemyapi.dev shows all collaborators per project and allows reviewing key access from a browser. For team leads who want a quick terminal view:

storemyapi share list    # collaborators on the linked project
storemyapi projects      # all projects you own or have access to

Checking for drift

If you're unsure whether your local .env is in sync with the cloud:

storemyapi audit

Shows:

• Keys in cloud but missing locally
• Keys in .env not yet pushed to cloud
• Keys that exist in both places but with different values