Skip to main content
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.
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.

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, 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:

Your accounts only

You can only share accounts you connected yourself.

Channels Token is in

You can only share into a channel Token has been added to.

No outsiders

A personal account cannot be shared into a channel that includes people from outside your team.

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:
1

If you name an account

Tell Token which account to use and it uses that one.
2

For your own data

When you have your own account shared in the channel, Token uses yours, so your data comes from your connection.
3

Otherwise, the channel default

Each channel can have a default account per service. You can set which one is the default.
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.

What admins control

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

Monitor activity

/token-audit shows every action Token took, in which channel, the decision made, and who approved it.

Manage rules

/token-rules lists the auto-approval rules Token has learned, so an admin can review or remove any of them.

Limit tools

Through approvals, an admin can require sign-off for, or block, a tool in a specific channel or across the whole team.

Configure the team

/token-config sets who the admins are, which email domains count as internal, and more.
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.