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

# Teams and accounts

> How Token works when a whole team shares it. Who connects what, who can share it, and what admins control.

Token is one assistant shared by your whole team. Everyone talks to the same
Token, but it keeps each person's accounts separate and only ever uses what has
been shared in a given channel. Here is how that works.

## Everyone brings their own accounts

When you connect a tool, you connect **your own** account, and it belongs to you.
Two teammates can each connect their own account for the same service, for
example their own inbox or calendar, and Token never mixes them up.

<Note>
  Connecting is per person. The account you connect is tied to you, not to the
  whole team, and no one else can use it until you share it.
</Note>

## Sharing is yours to control

Connecting an account does not expose it anywhere. For Token to use it in a
channel, the account has to be [shared with that channel](/integrations), and
only you, its owner, can share an account you connected. An admin cannot share
your account for you.

A few guardrails keep sharing safe:

<CardGroup cols={3}>
  <Card title="Your accounts only" icon="user-lock">
    You can only share accounts you connected yourself.
  </Card>

  <Card title="Channels Token is in" icon="hashtag">
    You can only share into a channel Token has been added to.
  </Card>

  <Card title="No outsiders" icon="shield-halved">
    A personal account cannot be shared into a channel that includes people from
    outside your team.
  </Card>
</CardGroup>

## When two people share the same tool

If two teammates each share their own account for the same service with the same
channel, both become available there. Token chooses which to use like this:

<Steps>
  <Step title="If you name an account">
    Tell Token which account to use and it uses that one.
  </Step>

  <Step title="For your own data">
    When you have your own account shared in the channel, Token uses yours, so
    your data comes from your connection.
  </Step>

  <Step title="Otherwise, the channel default">
    Each channel can have a default account per service. You can set which one is
    the default.
  </Step>
</Steps>

<Check>
  Token only ever acts as an account that has actually been shared in that
  channel. It will not reach for a connection that is not in scope there.
</Check>

## What admins control

Admins do not get to reach into other people's accounts, but they govern how
Token is used across the team.

<CardGroup cols={2}>
  <Card title="Monitor activity" icon="list-check">
    [`/token-audit`](/slash-commands) shows every action Token took, in which
    channel, the decision made, and who approved it.
  </Card>

  <Card title="Manage rules" icon="sliders">
    [`/token-rules`](/slash-commands) lists the auto-approval rules Token has
    learned, so an admin can review or remove any of them.
  </Card>

  <Card title="Limit tools" icon="ban">
    Through [approvals](/permissions), an admin can require sign-off for, or
    block, a tool in a specific channel or across the whole team.
  </Card>

  <Card title="Configure the team" icon="gear">
    [`/token-config`](/slash-commands) sets who the admins are, which email
    domains count as internal, and more.
  </Card>
</CardGroup>

<Note>
  Admins govern Token at the channel and team level, and can always stop a share
  or remove a rule. They cannot act as, or hand out, an account that someone else
  connected.
</Note>