> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xysq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams

> Shared memory vaults for teams — everyone on the same page, across every agent.

Teams give your group a shared vault. Memories and knowledge stored in a team vault are available to every member — regardless of which agent they're using. Your personal vault stays separate. Team context lives in the team vault.

<video width="100%" controls autoPlay loop muted playsInline style={{ borderRadius: "12px" }}>
  <source src="https://storage.googleapis.com/xysq_public/TeamsLaunch10.mp4" type="video/mp4" />

  Your browser does not support the video tag.
</video>

## How it works

A team vault is a memory bank shared by a group of users. Any member with write access can add memories. Any member with read access can recall them.

Team vaults work exactly like personal vaults: the same MCP tools, the same recall quality, the same Organise file uploads. The difference is scope. Instead of one person's context, it's the whole team's.

```
What has the team decided about the payment integration?
```

```
Retain to the team vault: We're going with Stripe, not Paddle. Decision made on the 14th.
```

Both calls look the same from inside your agent. xysq routes them to the right vault based on which team you're working with.

## Roles

Every member of a team has a role that controls what they can do.

| Role                | List | Recall | Retain | Delete | Manage members | Delete team |
| ------------------- | ---- | ------ | ------ | ------ | -------------- | ----------- |
| **ro** (read only)  | ✓    | ✓      | —      | —      | —              | —           |
| **rw** (read/write) | ✓    | ✓      | ✓      | —      | —              | —           |
| **admin**           | ✓    | ✓      | ✓      | ✓      | ✓              | —           |
| **owner**           | ✓    | ✓      | ✓      | ✓      | ✓              | ✓           |

The person who creates the team is automatically the owner. Ownership can be transferred to any other member.

## Creating a team

Go to **Teams** in [app.xysq.ai](https://app.xysq.ai). Click **New Team**. Fill in a name and an optional description. That's it — your team vault is ready.

<Note>
  Each team gets its own independent vault. There is no limit on the number of teams you can create, but each team vault counts against the team memory quota on your plan.
</Note>

## Adding members

Invite people by email. Open the team's **Settings** page, find the **Invite Member** card, type their email, pick a role, and click **Send invite**.

1. Go to **Teams** in [app.xysq.ai](https://app.xysq.ai) and open your team's **Settings**
2. In the **Invite Member** card, enter the person's email (e.g. `teammate@company.com`)
3. Choose their role, then click **Send invite**

We email them a link that expires in 15 days. They click it to join. If they don't have a xysq account yet, they can sign up with the same email and the invite drops them straight into the team. Pending invites show up on the Settings page until they're accepted.

Set their role when you invite them. You can change it later.

<Note>
  If your team is part of an organisation, the invite field doubles as a picker: start typing to add an existing org member to the team right away, or type any email to send an invite link.
</Note>

## Managing a team

Open the team from the Teams page and click **Settings**. From there you can:

* Rename the team or update its description
* Invite new members
* Change a member's role
* Remove a member
* Transfer ownership
* Delete the team

Deleting a team permanently removes the vault and all memories in it. This cannot be undone.

## Using the team vault with your agent

Once your agent is connected to xysq, it works with team vaults as naturally as your personal one. There's nothing extra to paste — no separate connection, no team ID.

**Retaining is explicit.** To store something in a team vault, name the team:

```
Retain to the Acme Engineering team vault: We're going with Postgres, not MySQL. Final decision.
```

Your agent passes the team along on that call. With no team named, a retain goes to your personal vault only — nothing is broadcast to a team by accident.

**Recall is controlled by the "Include in recall" toggle.** Each of your team memberships has an **Include in recall** toggle on its card at [app.xysq.ai/teams](https://app.xysq.ai/teams):

* **On** → that team's memories are folded into your recalls automatically, alongside your personal vault.
* **Off** → recall skips the team. You can still browse its vault in the web UI, and you can still scope to it explicitly in a prompt.

The toggle takes effect on your agent's next call — no reconnect, no restart. This keeps your standing recall scope deliberate: you opt each team in.

```
Before we start, recall what the Acme Engineering team has decided about the payment integration.
```

Good team memories capture **who decided**, **what was decided**, and **when**. Use the team vault for shared facts and decisions; keep personal preferences in your personal vault.

## Team apps

A team can connect external tools so their activity flows into the team vault. Open a team and use the **Apps** tab (`/teams/:teamId/apps`).

**GitHub** is live: connect a team's repositories and pull requests, reviews, comments, and pushes are synced into the team vault, tagged by repo. Connecting and choosing repos is an admin or owner action; any member can recall what's synced. See the [GitHub integration](/integrations/apps/github) for the full setup.

## Team vault limits

Team memory quota is separate from your personal quota. The total memories across all teams you own count against your plan's team memory limit.

Members you invite to your team do not affect your quota. They write memories using their own allocation. Check your current usage in **Dashboard → Teams**.