CLI reference
storeenv grant
Change a member's role, scope, expiry or production access.
zsh
$ cd ~/code/my-app$ storeenv grant @bea --role viewerUpdated @bea: viewer, production off, scope all
$ storeenv grant <user>
Arguments
<user> | The member, as @username. |
Flags
--role <viewer|editor|admin> | New role. One of: viewer, editor, admin. |
--all | Grant the whole project. |
--keys <value> | Specific secrets: backend/.env.production:DB_HOST,DB_USER. |
--files <value> | Whole files: backend/.env.production. |
--add | Add to the existing scope (default replaces it). |
--expires <value> | 24h, 7d, 30d or never. |
--prod | Turn production access on or off (owner only). |
Good to know
- Narrowing someone's access removes their key shares for what they can no longer read, at once.
Related commands
Global flags
--project <value> | Project as <namespace/name> or its id (default: .storeenv.json, then this repository's remotes). |
--env <value> | Environment name. |
--json | Machine readable output. |
--yes, -y | Skip confirmations. |
--color | Coloured output (--no-color to turn off). Default: true. |
--verbose | Show 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-unsigned | pull 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. |