Projects & organizations

Organizations

An organization owns everything: projects, teams, and membership. People join by invitation — send one from the Users page; the invite carries a link the recipient redeems to create their account and land in the organization.

You can belong to several organizations. The account menu at the bottom of the sidebar switches between them and creates a new one — unless the Instance keeps organization creation to its operators.

Organization settings (rename, and instance-level concerns on self-hosted installs) live on the Settings page.

Projects

A project is one product's spec: its artefacts, workstreams, Tasks, and its connection to source control. Create projects from the Projects page.

Project settings cover:

• General — name and description.
• Teams — which teams can edit the project (see below).
• Git — the repository binding for publishing, available once the source-control integration is configured.

Teams and the edit gate

Teams group people; projects grant edit access to teams. Anyone in the organization can browse a project's spec — reading is never gated — but editing requires membership of a team the project has granted access to.

Team membership is managed by the team's members themselves, not solely by an owner. Removing someone from the organization removes them from every team and revokes the access that flowed from those memberships.

Personal settings

Each person has their own settings, separate from any organization:

• Preferences — personal display options.
• Access tokens — the credentials agents hold: ones you issued and pasted, and ones granted when you signed in to an agent. Each acts as you; everything done with one is attributed to you and marked as agent work, and revoking it here cuts that agent off.