> ## Documentation Index > Fetch the complete documentation index at: https://docs.current.orinlabs.ai/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Connect Current to the systems your team already uses. An integration connects your Current workspace to an external service, such as Slack or Salesforce. The connection does two things. Your workflows read the data of that service, and your team talks to the Current agent in your chat tool. Read this page first. It tells you who makes a connection, what you need before you start, and what Current does with your access. ## How a connection works Your workspace holds one connection for each provider. One admin makes that connection, and the whole workspace uses it. The connection carries the access of the account that signs in. Current reads what that account reads. Current writes what that account writes. No connection gives Current more access than the person who made it. One connection serves every member. You do not sign in for yourself. If your workspace already shows **Connected** for a provider, you have nothing to do. ## The providers Read public channels, messages, and users. Send messages and files. Talk to the agent in a channel. Talk to the agent in a chat, a group chat, or a channel. Needs a second part: the app package. Find sites. Read files and write files. Read the pages that you select. Query and read records. Three ways to connect, for orgs with an API-only user. ## How much work each one is Four of the five providers need one sign-in and no more. Two need work in the external service as well. Read this table before you plan your time. | Provider | Time | Work outside Current | | --------------- | ------------------ | ----------------------------------------------------------------------------- | | Slack | 5 minutes | Invite the bot to each channel that the agent must answer. | | Notion | 5 minutes | Select the pages at sign-in. Share each new page later. | | SharePoint | 2 minutes | None. | | Microsoft Teams | 30 minutes or more | Your Teams administrator uploads an app package and sets its availability. | | Salesforce | 15 minutes or more | Your Salesforce administrator makes a connected app, or supplies an API user. | Plan the Microsoft Teams installation with your Teams administrator first. The connection alone delivers no messages. The bot arrives in a separate app package, and only a Teams administrator uploads it. ## Before you start You need the **admin** role in the Current workspace. Only an admin connects, repairs, or removes an integration. A member opens the **Integrations** page and reads the status of each provider. A member sees no buttons, and the page shows `Workspace admins manage integrations.` Ask an admin to make the connection. Some providers also need a second person, with rights in the external service: | Provider | Who else you need | | --------------- | ----------------------------------------------------------------------------------------------------------------- | | Slack | A person who can install an app in your Slack workspace. Many workspaces ask a Slack administrator to approve it. | | Microsoft Teams | A Teams administrator, to upload the app package and set its availability. | | SharePoint | A Microsoft account that opens every site your workflows use. | | Notion | A Notion user who shares the pages your workflows use. | | Salesforce | A Salesforce administrator, for the connected app or the API user. | Find this person before you start. A connection stops in the middle when you must wait for someone else. ## Which account to sign in with This is the most important decision on the page, and you make it in a few seconds during the sign-in. Think about it now. The connection keeps the access of the account that signs in. When that account loses its access, the connection stops. The connection stops when a person leaves the organization. Do not sign in with a personal account. Sign in with an account that stays, such as a service account of your organization. Slack and Microsoft Teams are exceptions. Both install an app that has its own identity, so the agent posts as **Current** and not as you. ## Security Current encrypts every access token in the database. Current never shows a token. The API never sends a token back to the portal. The agent posts as the Current bot in Slack and in Microsoft Teams. Current reads no message as you, and it sends no message as you. Where a provider gives a token with an expiry, Current renews the token before it expires. You repeat no sign-in each day. Slack tokens and Notion tokens have no expiry, so Current renews neither. When Current adds a permission to a provider, an existing connection does not receive it. Connect the provider again to grant the new permission. See [Repair a connection](/connect#repair-a-connection). ## Questions you may have No. Two limits apply at the same time. The permission list limits what Current asks for. Each provider page gives that list, with the purpose of each permission. The account limits what those permissions reach. An account that opens three SharePoint sites gives a connection that sees three sites. A member sees what your workflows and your agent show. The connection adds no separate browser of the external service. A member sees no token and no credential. The portal never receives them. Yes. A connection belongs to one workspace. A second workspace needs its own connection, and one admin of that workspace makes it. Current removes the stored token and stops every workflow that uses the provider. The data stays in the external service. Current deletes nothing there. The projects, the field values, and the observations that Current already holds stay in your workspace. No. Connect the providers that your workflows use. An unconnected provider stops no other provider. ## Next The procedure that applies to every provider. What each message means, and what to do about it.