Set it up once for the whole team.

An organization is a named account with members, roles and invitations, and creating one is free. Invite people by email; an invitation is valid for 14 days. Every organization starts with five built-in roles. Copy one to make your own, for example Admin with billing rights. The account service checks what someone may do at the moment they do it, rather than going by the role's name.

An organization workspace is set up once, with a name, a description and its repositories attached, and appears in the sidebar of every member with a seat. Each workspace is open, request-to-join or invite-only. Joining adds rows to your sidebar and clones nothing until you ask. Leave is never refused, and leaving deletes nothing: the workspace becomes an ordinary workspace of your own.

An organization can publish a setting at one of three levels. Recommended sets the value once on each member's device, and members can change it. Enforced applies everywhere and is locked, and the setting names the organization that set it. Evaluate changes nothing and reports how many devices would change. Your own value is kept under an enforced one and comes back when the organization stops managing it. Settings that describe your machine, and anything in your keychain, can never be managed.

Prompt templates an organization publishes appear in every seat holder's template list next to their own, with a badge naming the organization. Each template is a list of numbered revisions, and proposing a revision and publishing it are separate permissions. Members always get the current revision. An organization prompt may not start a line with ! or /, or attach a file with @path, and Plexus strips those on your machine as it types the prompt.

Cross-device sync carries your settings, workspaces and projects, including per-repository overrides such as a review prompt, to every machine you sign in on. It is off on every machine until you switch it on there, and it shows a list of everything that would leave the computer before anything does. Sessions, worktrees, transcripts and hook scripts are never synced. A seat includes sync on the seat holder's own machines, and the organization sees nothing of what they sync.

An organization plan is billed monthly, per seat. A seat carries shared workspaces, managed settings, organization prompts and sync. A member without a seat is still a full member, and sessions, worktrees, review, hooks and pull requests work exactly the same for them. Setting the seat count to zero is allowed. When a plan lapses nothing is deleted: shared workspaces stay on each machine and stop updating, and enforced settings keep their last value.