[{"data":1,"prerenderedAt":207},["ShallowReactive",2],{"site-nav-marketing":3,"feature-teams":36,"features-all-nav":190},{"features":4,"compare":23},[5,8,11,14,17,20],{"label":6,"to":7},"Sessions & status","\u002Ffeatures\u002Fsessions-and-status",{"label":9,"to":10},"Review","\u002Ffeatures\u002Freview",{"label":12,"to":13},"Worktrees & hooks","\u002Ffeatures\u002Fworktrees-and-hooks",{"label":15,"to":16},"Git & issues","\u002Ffeatures\u002Fgit-and-issues",{"label":18,"to":19},"Stacks","\u002Ffeatures\u002Fstacks",{"label":21,"to":22},"Teams","\u002Ffeatures\u002Fteams",[24,27,30,33],{"label":25,"to":26},"vs Claude Code","\u002Fcompare\u002Fclaude-code",{"label":28,"to":29},"vs Claude Squad and Nimbalyst","\u002Fcompare\u002Fclaude-squad-and-nimbalyst",{"label":31,"to":32},"vs Conductor","\u002Fcompare\u002Fconductor",{"label":34,"to":35},"vs Cursor","\u002Fcompare\u002Fcursor",{"id":37,"title":38,"body":39,"description":98,"draft":99,"extension":100,"faq":101,"hero":117,"meta":121,"navTitle":21,"navigation":122,"order":123,"path":22,"sections":124,"seo":186,"slug":187,"stem":188,"__hash__":189},"features\u002Ffeatures\u002Fteams.md","Teams: organizations, managed settings, prompts",{"type":40,"value":41,"toc":93},"minimark",[42,47],[43,44,46],"h2",{"id":45},"read-more","Read more",[48,49,50,59,65,81,87],"ul",{},[51,52,53,58],"li",{},[54,55,57],"a",{"href":56},"\u002Fdocs\u002Faccount","Your Plexus account",": sign-in, organizations and devices",[51,60,61],{},[54,62,64],{"href":63},"\u002Fdocs\u002Froles","Roles and permissions",[51,66,67,71,72,76,77],{},[54,68,70],{"href":69},"\u002Fdocs\u002Fshared-workspaces","Shared workspaces",", ",[54,73,75],{"href":74},"\u002Fdocs\u002Fmanaged-settings","Managed settings"," and ",[54,78,80],{"href":79},"\u002Fdocs\u002Forg-prompts","Organization prompts",[51,82,83],{},[54,84,86],{"href":85},"\u002Fdocs\u002Fsync","Cross-device sync",[51,88,89],{},[54,90,92],{"href":91},"\u002Fdocs\u002Fbilling","Plans, seats and billing",{"title":94,"searchDepth":95,"depth":95,"links":96},"",2,[97],{"id":45,"depth":95,"text":46},"Organizations, shared workspaces, managed settings, a shared prompt library and sync for teams on Claude Code. Seats are paid; the core app stays free.",false,"md",[102,105,108,111,114],{"question":103,"answer":104},"Does a member without a seat lose access to anything?","No. They stay in the organization with their role and use Plexus exactly as before. A seat adds shared workspaces, managed settings, organization prompts and cross-device sync on their own machines.",{"question":106,"answer":107},"Can an admin see what I sync?","No. Sync is attached to your personal account, not to the organization. Paying for your seat gives you the feature and shows the organization nothing, and there is no admin view of it.",{"question":109,"answer":110},"Does our code go through Plexus servers?","No. Agents run in terminals on each developer's machine, and pull request and issue traffic goes directly from that machine to GitHub or Bitbucket. Sync sends settings, workspaces and project details such as names and remote addresses, only after you have reviewed the list.",{"question":112,"answer":113},"Who can buy seats?","The organization's owner. Admins manage members and give out the seats that are already paid for. To let admins handle billing as well, copy the Admin role and tick Manage billing on the copy.",{"question":115,"answer":116},"What happens if the plan lapses?","Nothing you made is deleted. Shared workspaces stay on each machine with everything in them and stop updating, enforced settings keep their last value, published prompts keep working, and sync stops. Starting a plan again picks up where it left off.",{"eyebrow":118,"headline":119,"lead":120},"Teams & organizations","Set it up once for the whole team.","Organizations add shared workspaces, managed settings and a shared prompt library to the free app. They come with seats on a paid plan. Agents, code and sessions still run on each developer's own machine.",{},true,6,[125,134,145,162,170,177],{"id":126,"heading":127,"body":128,"state":129,"docsPath":63,"sim":130},"organizations","Organizations and roles","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.","neutral",{"view":131,"anchors":132,"note":133},null,[],"No app-sim view shows Settings → Organizations. Use a static panel, or leave this section without an illustration.",{"id":135,"heading":136,"body":137,"state":138,"docsPath":69,"sim":139},"shared-workspaces","Workspaces that arrive ready","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.","working",{"view":140,"anchors":141,"note":144},"sessions",[142,143],"workspace","tree","The demo has no organization badge on the workspace. Point at the workspace switcher and the tree.",{"id":146,"heading":147,"body":148,"state":149,"docsPath":74,"sim":150},"managed-settings","Settings the organization manages","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.","needs-you",{"view":151,"hooksScope":152,"anchors":153,"crop":156,"note":161},"hooks","global",[154,155],"settings","hooks-nav",{"x":157,"y":158,"w":159,"h":160},0,48,1440,852,"The app-sim Settings screen has no managed-setting badge or lock. Use it only as context.",{"id":163,"heading":164,"body":165,"state":166,"docsPath":79,"sim":167},"org-prompts","A shared prompt library","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 \u002F, or attach a file with @path, and Plexus strips those on your machine as it types the prompt.","delegating",{"view":131,"anchors":168,"note":169},[],"No app-sim view shows the template list. Leave this section without an illustration or use a static panel.",{"id":171,"heading":172,"body":173,"state":129,"docsPath":85,"sim":174},"sync","Your setup on every machine","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.",{"view":131,"anchors":175,"note":176},[],"No app-sim view for Settings → Sync.",{"id":178,"heading":179,"body":180,"state":181,"docsPath":182,"sim":183},"seats","Seats, and what stays free","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.","merged","\u002Fdocs\u002Fbilling#seats",{"view":131,"anchors":184,"note":185},[],"Pair with the live plans from the pricing API rather than the app-sim.",{"title":38,"description":98},"teams","features\u002Fteams","FKprdWZhAnCCwpRK0iBUg7bK4aYe_SFX5GcYTSaxGos",[191,194,197,200,203,206],{"path":7,"title":192,"navTitle":6,"description":193},"Parallel Claude Code sessions with live status","Run many Claude Code agents at once, each in its own git worktree, and see which one needs you: working, needs you, delegating or idle, across every repo.",{"path":10,"title":195,"navTitle":9,"description":196},"Review AI agent changes like a pull request","A PR-style diff of each Claude Code session's worktree, inline comments the agent acts on, AI review, a review-and-fix cycle and the PR conversation.",{"path":13,"title":198,"navTitle":12,"description":199},"A git worktree per agent, set up by your own hooks","Every Claude Code session gets its own git worktree, your .env files, a block of dev-server ports, and your Create, Run and Teardown hooks at three levels.",{"path":16,"title":201,"navTitle":15,"description":202},"Git client, PRs and GitHub issues for AI agents","A git client per Claude Code session and per repo, GitHub and Bitbucket pull requests with CI status, and GitHub Issues and Projects boards in one window.",{"path":19,"title":204,"navTitle":18,"description":205},"Stacked pull requests and ordered merging for Claude Code sessions","Stack Claude Code sessions on each other's branches. Plexus keeps every branch synced as the agents work, shows the stack as a map, and merges it in order, as a GitHub stack or through a merge queue.",{"path":22,"title":38,"navTitle":21,"description":98},1792695507515]