# Work as a team (/teams)



When several people work on one repository with Jinion, their agents make choices the others never see: a library
picked, a convention set, a trade-off accepted on purpose. Team workspaces share those choices. Each agent records the
decisions that matter as it works, and every teammate's agent keeps to them once they are in their code.

## How it fits together [#how-it-fits-together]

| Piece     | What it is                                                    | Where                                                                   |
| --------- | ------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Workspace | Your team: its members, its projects and their decisions      | [cloud.jinion.co](https://cloud.jinion.co)                              |
| Project   | One repository in a workspace                                 | cloud.jinion.co, and `jinion.config.json` in the repository             |
| Decision  | A choice an agent recorded, with why and what was turned down | In your conversations, `/decisions`, and the archive on cloud.jinion.co |

## Set up a team [#set-up-a-team]

1. Sign in on [cloud.jinion.co](https://cloud.jinion.co) with the account you use in Jinion's apps, and create a
   workspace. Its address is made from its name, and you can change both later.
2. [Link your repository](/link-a-repository) to a project from Jinion, with `/link`, and commit the
   `jinion.config.json` it writes.
3. On the workspace's **Members** page, invite your team by email.
4. [Connect GitHub](/github-app) on the project's page, so decisions reach `main` through squash and rebase merges too.

A teammate who stays in Codex, Claude Code or Cursor reads the same decisions there, with
[`jinion mcp`](/other-agents).

## Roles [#roles]

| Role   | Can                                                                                                              |
| ------ | ---------------------------------------------------------------------------------------------------------------- |
| Owner  | Everything an admin can, and delete the workspace or hand it to someone else. There is one                       |
| Admin  | Invite and remove members, change roles, add projects, answer access requests, connect GitHub, archive decisions |
| Member | Read the project's decisions, and record them as they work                                                       |

Everyone in a workspace reads every one of its projects' decisions.

## Invite people [#invite-people]

An admin invites one or several addresses at once, as admins or members. Each gets an email with a link that works for
7 days, and only signed in with the address it was sent to, so a forwarded link lets nobody else in. An invite to an
address with no Jinion account yet works too: they sign up and land in the workspace.

<Callout>
  During the private beta, joining a workspace doesn't activate a Jinion account by itself: a new teammate still needs an
  invite code to start using the apps.
</Callout>

## Ask for access [#ask-for-access]

Someone who opens a linked repository without being in its workspace sees whose project it is, and can ask to join,
from `/link`, the desktop's **Decisions** page, or `jinion link`. The workspace's admins get an email and answer on the
workspace's **Access requests** page. Approving makes them a member; declining lets them ask again after a week.