Organizations
An organization owns projects and groups people. Members have a role —
OWNER or MEMBER. Creating an org makes you its first OWNER and creates a
matching namespace.
Manage organizations
Members
Users are referenced by email or name — the CLI resolves them to a user id (an exact email is unambiguous).
Remove a member
Only an org OWNER can remove a member; a team MAINTAINER manages team membership, not organization membership. The server refuses to remove the last OWNER. Removal ends the person's organization membership: org-wide (workspace-member) access, any OWNER authority over the organization's namespace, and their memberships in its teams, so Project access shared with those teams ends too. Project grants they issued on Projects owned by the organization are deleted.
By default their direct personal grants on Projects owned by the
organization are kept, as before. Add --revoke-direct-project-grants to delete
those grants in the same removal. Independent resource shares and public
access are not changed either way. The confirmation states which applies;
--yes skips it.
--revoke-direct-project-grants needs a server that supports it. An older
server rejects the request and nobody is removed; the CLI reports this and
never retries without the option. Without the option, the CLI sends the same
request as earlier versions.
In TypeScript, the same opt-in is an optional third argument:
An older server makes this throw OrganizationMemberRemoveRevokeUnsupportedError.
Permissions
Permissions are enforced by the server, not the CLI — it sends the request with your token and surfaces the result.
| Action | OWNER | MEMBER |
|---|---|---|
| Create / edit project | ✓ | ✓ |
| Delete project | ✓ | ✗ |
| Create / delete files & episodes | ✓ | ✓ |
| Manage org members | ✓ | ✗ |
Organization and team commands talk to the server's GraphQL endpoint
(POST /graphql) using the same token as every other command.