Organization and team sync

The Organization panel is where you share projects with your organization and decide who can work on them. Team sync keeps each shared project's plan, tickets, and history the same on every member's computer.

Where to find it

Select Organization in the sidebar. The item only appears when the account you are signed in with belongs to an organization. A solo account never sees it.

What the panel shows depends on your account:

• An organization on a team plan. You see the full panel, described below.
• An organization without a team plan. You see an upgrade prompt titled "Teams require a Team plan". Sharing, teams, and access controls stay hidden.
• No organization. If the panel opens while you are not in an organization (for example, after an org admin removed you), it reads "You're not part of a team right now". Select Manage teams to open the account site, or Refresh to check again.

Organizations, memberships, org roles, and seats are managed on the account site, not in the app.

Seats and credits

Every active member of the organization is a billed seat. Viewers, editors, maintainers, and org admins all count the same.

Team credits are pooled. The organization's monthly budget is the number of seats times the per-seat credits of its plan (1,500 credits per seat on Team Starter, 6,000 on Team Max). The Organization panel labels these plans Team Basic and Team Pro. While your active organization has a team plan, your LLM features draw from that shared pool, not from a personal balance.

What you see

A card at the top of the panel shows your org role, your teams, and, when available, your seat and the size of the shared credit pool. An org admin also gets a Manage members in Clerk link.

If you belong to no team, the card says so: "You're not on any team yet, so no projects are shared with you. Ask an org admin to add you."

Below the card are 4 tabs: Projects, Teams, Members, and Access.

Projects tab

The Projects tab lists every project your organization has shared. Each row shows the project name, a badge for each team it is shared with, and the maintainers. A line under the name explains your own access in words, such as "Editor via Backend", "Maintainer (org admin)", or "Viewer (set by a maintainer)".

Each row offers exactly one action:

• Open when the project is already on this computer. The app switches to it.
• Set up when you have access but the project is not on this computer yet.
• Request access when the project is shared only with teams you are not on. After you ask, the button reads Requested.

A maintainer also sees Manage access →, which opens the Access tab on that project.

When a project has been shared with you but is not set up here, a Shared with you card appears at the top of the tab. Each line reads like "Backend shared Billing API with you." with Set up and Later. Later hides the line until you switch tabs or leave the panel. The project stays in the list below.

Teams tab

A team is a named group of members. Teams decide who can edit which projects.

Every organization has a default team called Everyone. New members join it automatically, and new shares go to it unless you pick other teams. You can rename it, but you cannot delete it.

Each team card lists its members, the projects the team can edit (Edits:), and the projects it can only read (Views:). Members marked Team admin can manage that one team's roster.

Members tab

The Members tab lists everyone with a seat. Each row shows the member's name, org role (Org admin or Member), their teams, and their seat. An org admin sees Change role in Clerk on each row, which opens the account site. Roles and seats cannot be changed inside the app.

If you maintain a project or are an org admin, a Pending requests card sits above the roster whenever someone has asked for access to a project.

Access tab

The Access tab answers "Who can work on this project". It opens on the project you have open. Use the Project picker to switch to another project you maintain.

The tab has 4 sections:

• Maintainers: people who decide who can work on the project. Org admins always appear here.
• Teams with edit access: everyone on these teams can change the project, within the editor limits under Roles.
• Teams with view access: everyone on these teams can read the project but not change it.
• Individual overrides: people whose access is set for them directly instead of through a team. Only maintainers see the names. Everyone else sees "Only maintainers can see who is set individually."

If the open project is not shared, the tab offers Share it.

How to use it

Share a project

Any member can share a project that exists on their computer. The person who shares it becomes its first maintainer.

1. Open Organization, then the Projects tab.
2. Select Share a project.
3. Pick the project under Project. Only projects not already shared are listed.
4. Under Teams, check the teams that should work on it. The default team is preselected.
5. Select Share.

Everyone on the teams you picked becomes an editor of the project. If every project on this computer is already shared, the button is disabled, and its tooltip reads "All your projects are already shared".

Set up a shared project on this computer

1. Select Set up on the project's row, in the Shared with you card, or in the notification bell.
2. Select Change repo folder and pick your local clone of the project's repository. You can skip this and set the folder later.
3. Select Set up.

The project appears in your projects once its plan and history finish downloading. To point it at a different folder later, open Dashboard, then the Team tab, and select Change next to the repo folder.

Create a team and add members

Only org admins can create or delete teams.

1. Open the Teams tab.
2. Type a name in Team name and select Create team.
3. On the new team's card, check the members to add. Check Team admin if they should manage this team's roster.
4. Select Add.

Org admins and that team's admins can rename the team and add or remove members. Before a removal, the app names the projects the person would lose edit access to. Everyone else sees the card read-only.

Change who can work on a project

Only maintainers can change access. Others see "Only maintainers can change access."

1. Open the Access tab on the project, or select Manage access → on its row.
2. To add someone, use Add a person or team..., pick a person or team and a level (viewer, editor, or maintainer), then select Add.
3. To change a level, change it on the row and confirm with Change access.
4. To remove someone, select Remove and confirm with Remove access.

A project must always keep one maintainer, so the app refuses a change that would remove the last one. If you change your own access, the confirmation warns you first.

Answer an access request

1. Open the Members tab (or the Access tab) and find the request under Pending requests.
2. Pick the level to give. It defaults to editor.
3. Select Approve or Deny.

Roles

Each member has one org role from the account site (org admin or member) and, on each shared project, one level of access. A member's access comes from their teams, unless a maintainer sets a level for them directly, which then takes priority over their teams. Org admins are always maintainers of every project in the organization.

When an editor tries a maintainer-only change, the app refuses it and asks them to get a maintainer to make it. If your level changes while you work, a message tells you the new level.

Sync in daily use

Every edit is saved on your computer first, then sent to the rest of your organization. Teammates' changes arrive in the background, and open panels refresh without a reload. Every shared project syncs, including the ones you do not have open.

The sync indicator

A colored dot in the header shows the open project's sync state. It is hidden for projects that are not shared.

A number next to the dot counts unresolved conflicts. Click the dot to open a popover with Last synced seq (the position of the last change this computer received), the conflict count, and Present now (who else has the project open, or "No one else online"). When the project is offline or revoked, the popover offers Reconnect. When an update is required, the button reads Update the app to reconnect and stays disabled. Clicking Conflicts opens the Dashboard's Team tab.

Dashboard Team tab

Dashboard → Team shows a status line naming the teams the project is shared with and your access. Below it are the Team Sync card (status, last synced seq, pending changes) and the Sync Conflicts card. See Dashboard for the card details.

Notification bell

On a team plan, a bell in the header collects what needs your attention. Its list includes:

• Projects shared with you that are not set up, each with Set up.
• Access requests waiting for your decision, which open the Members tab.
• A sync problem on the open project ("Access revoked", "Update required", or "Offline (N pending)"), which opens the Dashboard's Team tab.

When a project is newly shared with you during a session, a message appears with a Set up action.

Who changed what

Every synced change carries its author. On a shared project, the Logs panel adds a Changelog tab that lists each change in plain language, tagged to the person who made it or to their agent, with a filter by member. Changes made before the project was shared are grouped under "Before sharing". See Logs.

On team projects, tickets can also have an assignee. See Tickets.

Conflicts

A conflict is a change that did not apply cleanly. Each one appears as a card in Sync Conflicts on the Dashboard's Team tab.

Only a maintainer can resolve conflicts. Other roles see the same cards without buttons, with the note "Recorded on this computer only. A maintainer signed in here can resolve them; other devices don't see them." Conflict cards live on the computer where they happened.

Security

• Shared project data is encrypted at rest and in transit under a per-organization key. It is not end-to-end encrypted.
• Each computer enrolls itself the first time it syncs, with no setup on your part. Its private keys are stored in the operating system's keychain.
• Every change is signed by the computer that made it and linked to that computer's previous change. Each computer checks these signatures and links before applying a change. A change that fails the check is not applied, and an integrity conflict records it.
• In Version History, a verified change shows a small shield mark. Its tooltip reads "Signed by the author's device and verified on this computer."
• Access ends when a member is removed from the organization. There is no separate list of devices to revoke.

When your access is revoked, your local copy stays on your computer. Edits you make are kept and queued, but nothing reaches the organization unless access is restored. The app checks again every 5 minutes. If your app version is too old, the status is Update required and sync stops until you update.

What leaves your computer

For a shared project, these items sync to the organization: the project's details (name, description, goal, constraints, non-goals, tech stack, drift threshold), phases, tickets and their comments and reports, decisions, context nodes and links, file mappings, hooks, enforcement proposals, and taxonomy entries.

Some project settings never leave the computer: the project's MCP token, the project owner, the active ticket, the selected agent adapter, the lock state, the report setting, and the agent-artifact paths. The repo folder you pick during setup is also local to each computer.

Projects you never share do not sync.

Rules and limits

• The Organization panel needs a team plan. Without one, it shows an upgrade prompt.
• Sharing is open to any member. Changing access is maintainer-only. Creating and deleting teams is org-admin-only.
• The default Everyone team cannot be deleted.
• A project always keeps at least one maintainer.
• Conflict resolution is maintainer-only, and conflict cards stay on the computer where they happened.
• Deleting an organization or an account is immediate and cannot be undone. When an organization is deleted, its encryption key is destroyed, so its synced data can no longer be read. The only thing kept is one billing record, held for 30 days for billing disputes, then purged.

If something looks wrong

• There is no Organization item in the sidebar. Your account is not in an organization. An org admin must add you on the account site.
• The Projects tab is empty. You may be on no team. Ask an org admin to add you to one.
• A project row shows Request access. The project is shared only with teams you are not on. Request access, and a maintainer will review it.
• The indicator says Read-only. You are a viewer on this project. Ask a maintainer to change your level on the Access tab.
• A shared project you set up has not appeared. It appears once its plan and history finish downloading. If you select Set up again, the app replies that you have already set it up.