StoreEnv Beta
Documentation

Install the CLI, learn the model and look up every command.

CLI reference

storeenv invite

Invite people by email or StoreEnv username, with a role and scope.

Global flags
zsh
$ cd ~/code/my-app
$ storeenv invite bea@example.com --role editor
  Invitation sent to bea@example.com.
    Invite link: https://storeenv.app/invites/1e5bcdb096737b992e407587890d8e216ff03e98f17df2f9
  Keys are shared once they accept and set up their key.
$ storeenv invite <users..>

Arguments

<users>@username or email.

Flags

--role <viewer|editor|admin>Role in the project. One of: viewer, editor, admin. Default: viewer.
--keys <value>Specific secrets: backend/.env.production:DB_HOST,DB_USER.
--files <value>Whole files: backend/.env.production.
--expires <value>Access expiry: 24h, 7d, 30d.
--prodGive production access (owner only).
--message <value>, -mA note included in the invitation.

Good to know

  • Invite by email address or StoreEnv username. Someone without an account gets an email; they sign up and accept.
  • The new member shows as pending key share until a device that can read the secrets wraps the keys for them. Your next CLI command does that, or run storeenv share.

Related commands

storeenv membersstoreenv grantstoreenv sharestoreenv revoke

Global flags

--project <value>Project as <namespace/name> or its id (default: .storeenv.json, then this repository's remotes).
--env <value>Environment name.
--jsonMachine readable output.
--yes, -ySkip confirmations.
--colorColoured output (--no-color to turn off). Default: true.
--verboseShow debug details.
--api <value>API base URL of a self-hosted StoreEnv.
--trust-writer <value>Trust a writer for this run: @login=SE:XXXX-XXXX-XXXX.
--allow-unsignedpull and diff: use values that aren't signed by a trusted writer, after you confirm on a terminal (or with STOREENV_ALLOW_UNSIGNED=1). Never applies to run or copy.
Previous members Next grant