> ## 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. # Setting up tools > Connect an account and share it with a chat so Token can use it there. Token does its work through the tools you give it: your notes, your calendar, your tracker, and more. Two things have to happen before Token can use a tool in a chat. Sign in once to give Token its own access to a service. This creates the account. Token uses its own access, never your personal login. Make a connected account usable in a specific channel. A tool only works in the chats you have shared it with. Keeping these separate is what makes Token safe to use in shared channels: an account you connected is not automatically exposed everywhere. It only works where you have shared it. ## Your account vs Token's account When you connect an account, it's normally **your own**: it belongs to you, only you can share it, and Token uses it in the chats you choose to share it with. Two teammates can each connect their own account for the same service. Token can also have its **own account**, called the **agent account**. This is the identity Token acts as on its own behalf, rather than on behalf of a person. It works differently from a personal account in two ways: * It's **available in every chat by default**, with no per-chat sharing. Token uses it wherever it acts as itself. * It's the only account Token can use in **external chats** (channels with people outside your workspace), where personal accounts are never used. You connect it by signing in as the account you want Token to use (for example a dedicated `token@yourcompany.com`). There's one agent account per service, and setting it up is an admin action. ## The fastest way: just ask You usually do not need to leave the chat. Ask Token for what you need, for example "read our Notion," and if nothing is set up yet, Token posts a short **Set it up** card right there. The card shows what is missing, for example "No Notion is set up in this channel yet," with a **Set it up** button. Tapping it opens a private next step that only you can see. If you already connected the right account, choose it to **share it with this channel**. If you have not connected it yet, follow the link to connect it first, then share it. Once shared, the channel shows that the tool is set up, and Token can use it. Only the person who connected an account can share it. Sharing happens in a private step, so other people in the channel never see your other accounts. ## Using the dashboard You can also manage everything from the **dashboard**, which is the better place to see the whole picture: * **Integrations** lists every service and lets you **connect** a new account. * A channel's settings show which accounts are shared with it. From there you can share another account, set a default account for that channel, or **stop sharing** one. ## More than one account You can connect more than one account for the same service, for example two calendars or two inboxes. When a channel has access to several, you can mark one as the **default** for that channel, and Token uses that unless you tell it otherwise. Who can share which accounts, what happens when two teammates share the same tool with one channel, and what admins control. ## Turning access off * **Stop sharing** an account to remove it from a channel. The account stays connected and keeps working in other chats. * **Disconnect** an account to remove it entirely, so Token can no longer use it anywhere. ## Setting up does not bypass approvals Sharing a tool decides what Token *can* reach. It does not decide what Token is *allowed to do*. Even after a tool is set up, sensitive actions still go through [approvals](/permissions). The two layers work together.