CLI reference
storeenv orgs
Organizations: list, create, view, members, add, role, remove, leave, transfer, delete.
zsh
$ cd ~/code/my-app$ storeenv orgs create acme --name "Acme Inc"Created acme. You are its owner. Projects can now live under acme/.
$ storeenv orgs [action] [org] [login] [role]
Arguments
<action> | What to do with an organization. One of: list, create, view, members, add, role, remove, leave, transfer, delete. Default: list. |
<org> | Organization slug. |
<login> | @username. |
<role> | admin or member. |
Flags
--name <value> | Display name (create). |
--as <admin|member> | Role for add. One of: admin, member. Default: member. |
More examples
$ cd ~/code/my-app$ storeenv orgsORGANIZATION NAME ROLE MEMBERSacme Acme Inc owner 1
Other uses
storeenv orgs create acme --name 'Acme Inc' | Create an organization you own |
storeenv orgs add acme @neha --as admin | Add a member (only the owner can add admins) |
storeenv orgs transfer acme @neha | Hand the organization to a member; you stay admin |
Good to know
- An organization is a namespace for shared projects: create projects in it with storeenv init --namespace <org>.
- Organization roles (owner, admin, member) decide who may create projects in the namespace. Access to each project's secrets is still per project (storeenv invite, storeenv grant).
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. |