> ## 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. # Connect an integration > The procedure that applies to every provider, and how to repair or remove a connection. This page gives the steps that apply to every provider. Each provider page adds the steps for that provider only. Read this page one time. After that, go to the page of your provider. ## What the Integrations page shows Go to **Settings** > **Integrations** in the portal. The page shows one row for each of the five providers, in this order: Slack, Microsoft Teams, SharePoint, Notion, Salesforce. Each row holds four things: 1. The icon and the name of the provider. 2. A status badge, if a connection exists. 3. A grey line below the name. This line tells you the state of the row. 4. The buttons, if you are an admin. The grey line reads one of these: | The grey line | What it means | | -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Not connected.` | No connection exists. Your Current server holds the credentials, so you connect now. | | `Not configured on this server.` | Your Current server holds no credentials for this provider. You cannot connect it. Speak to your Current contact. | | `OAuth is not configured on this server — connect with credentials.` | Salesforce only. The sign-in option is unavailable, and the two credential options stay available. See [Salesforce](/integrations/salesforce#choose-how-to-connect). | | A name and a date, such as `Acme Corp — connected Mar 4, 2026` | The connection is live. The name is the account or the workspace that made it. | ## Connect In the portal, go to **Settings** > **Integrations**. Find the row of your provider. Read the grey line first. A row that reads `Not configured on this server.` cannot connect, and no button changes that. Click **Connect** on the provider row. The browser leaves the portal immediately. This is correct. The provider shows its own sign-in page. Sign in with the account that holds the data you want. The connection stops when the account loses its access. Do not use a personal account. Use an account that stays in the organization. Complete this step without a long pause. The link is valid for 10 minutes. The provider shows a permission list and asks for your consent. Read the list. Each provider page gives the same list, with the purpose of each permission. Click the button that gives the consent. The name of that button changes with the provider: **Allow**, **Accept**, or **Allow access**. The provider sends the browser back to the **Integrations** page. You return to the same page you started from. The provider row shows the green **Connected** badge. The grey line changes to the account name and today's date. A message confirms the connection. If a red message arrives instead, see [Messages after the sign-in](/troubleshooting#messages-after-the-sign-in). Click the chevron at the end of the connected row. A grey band opens below the row. The band names the account, the member who made the connection, and the granted permissions. Read the account name now. An account that surprises you is the one problem that is hard to find later. ## What the status badge tells you A live connection carries one of two badges. | Badge | What it means | What to do | | ----------------------- | ----------------------------------------------------- | --------------------------------- | | Green **Connected** | Current authenticates to the provider correctly. | Nothing. | | Red **Needs attention** | Current cannot authenticate to the provider any more. | Repair the connection. See below. | A disconnected provider carries no badge. The row goes back to `Not connected.` and shows the **Connect** button again. ### One failed request does not change the badge The badge answers one question only: does Current authenticate? It does not report every refusal. The connection keeps the **Connected** badge when the provider refuses a single request. A refusal of that type tells you about the request, not about the connection. Examples are an interface that your organization disables, a permission that the account does not have, and a rate limit. The tool that made the request reports the error. The other tools continue to operate. Read the run history of the action for the message of the provider. ## Repair a connection Repair a connection when the badge reads **Needs attention**. Current shows this badge after it fails to renew the token. Three things cause it: * A person cancelled the access at the provider. * A person changed the password of the account. * Your organization removed the account. Go to **Settings** > **Integrations**. Click **Reconnect** on the provider row. This button shows only while the badge reads **Needs attention**. A row with the **Connected** badge shows **Disconnect** only. Complete the same sign-in as before. The badge goes back to green **Connected**. For a Salesforce connection that uses a connected app or an API user, **Reconnect** opens the credentials form again. It opens no sign-in page. Salesforce shows no sign-in page to these accounts. See [Salesforce](/integrations/salesforce). ### Grant a new permission Use the same procedure to grant a new permission. Current asks for the full permission list each time you connect, so a reconnection grants the permissions that the first connection missed. Do this when a provider page tells you that an older connection has less access. The badge stays green in this case, because the connection still authenticates. The tool that needs the new permission reports the error. ## Disconnect Go to **Settings** > **Integrations**. Click **Disconnect** on the provider row. A dialog opens and names the consequence. Click **Disconnect** again to confirm. The badge goes away. The grey line goes back to `Not connected.`, and the **Connect** button comes back. A disconnection stops every workflow that uses the provider. Current removes the stored token, and the row goes back to the unconnected state. ### Remove the access at the provider as well A disconnection always removes the token from Current. It does not always cancel the access at the provider. | Provider | What Current cancels at the provider | | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | Slack | The token. Current cancels it. | | Salesforce, connected with the sign-in option | The token. Current cancels it. | | Salesforce, connected with a connected app or an API user | Nothing. Current holds a secret or a password, and it sends neither to a cancellation endpoint. | | Microsoft Teams, SharePoint, Notion | Nothing. | For the providers in the last two rows, the application stays in the list of the external service. Remove it there as well. The "Remove the integration" section of each provider page gives the steps. ## Questions you may have Check your role first. Only an admin sees the **Connect** button. A member sees the row, the badge, and the line `Workspace admins manage integrations.` If you are an admin, read the grey line. A row that reads `Not configured on this server.` has no working button. The link is valid for 10 minutes. After that, the portal reports `The connection link expired — try connecting again.` Click **Connect** again and complete the sign-in without a pause. Current makes a new link each time. No. A workspace holds one connection for each provider. A second connection replaces the first one. To change the account, connect again and sign in with the other account. No. A reconnection replaces the token. Your projects, your field values, and your observations stay in the workspace.