> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/integrations/salesforce-integration/reconnect-salesforce.md).

# Reconnect Salesforce or change the integration user

Reauthorize an existing Salesforce connection, switch its integration user, and troubleshoot login or credential errors.

Use **Reauthorize** to renew an existing Salesforce connection or authorize it with a different Salesforce user. For a first connection, follow the [package installation guide](https://docs.kernel.ai/integrations/salesforce-integration/package-installation-guide.md). Moving from 3.x to 4.x requires the [package migration guide](https://docs.kernel.ai/integrations/salesforce-integration/migrate-the-salesforce-package-from-3.x-to-4.x.md).

## Identify which connection needs attention

Kernel's Salesforce integration uses two separate authorizations:

| Connection                                           | What it enables                                                             | Where to check                                                                           |
| ---------------------------------------------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Kernel to Salesforce, using Salesforce OAuth         | Kernel reads or writes Salesforce as the user who authorized the connection | The selected Salesforce connection in Kernel and Salesforce's Connected Apps OAuth Usage |
| Salesforce package to Kernel, using a Kernel API key | Package requests such as feedback submissions                               | Kernel Setup in Salesforce and the failed operation's error                              |

Reauthorizing Salesforce does not replace the package's Kernel API key. A package showing **Connected** also does not prove that every Salesforce user can send feedback. See [feedback troubleshooting](https://docs.kernel.ai/integrations/salesforce-integration/report-data-issues.md#troubleshoot-a-failed-submission) for those errors.

## Before reauthorizing

1. In Kernel, select the correct environment and Salesforce connection. Confirm the Salesforce org URL. Sandbox and production connections need separate authorization.
2. Confirm which Salesforce username should run the integration. Changing a user's email address or selecting a user inside the package does not by itself replace the Salesforce OAuth authorization.
3. Have your Salesforce administrator check that this user is active, can use the Kernel Connected App, and has the [permissions needed for the enabled workflows](https://docs.kernel.ai/integrations/salesforce-integration/salesforce-integration-user-permission-matrix.md).
4. Make sure the person completing authorization can access that user's password and complete the Salesforce login requirements. If password-reset email goes to `integrations@kernel.ai`, arrange this with Kernel first. Use an approved secure method to share credentials.

Kernel's authorization window uses browser login and consent. If your integration user has an API-only license or profile, contact Kernel to confirm the supported authorization setup. Do not assume that API access alone means the user can complete this flow, or change licenses based only on a loading spinner.

## Reauthorize the selected connection

1. Stay signed into Kernel with your own Kernel account. You do not need a separate Kernel account for the Salesforce integration user.
2. In the same browser, log out of any existing Salesforce session for the target org so it does not reuse another user's login. This is separate from your Kernel sign-in.
3. In Kernel, open **Settings › CRM › Salesforce** and choose **Reauthorize** for the intended connection.
4. Choose **Salesforce login** to sign in with the integration user's Salesforce credentials. Use **Company sign-in** only when your administrator intends to authorize through the organization's SSO identity.
5. In the Salesforce window, check the org and username, complete login, and approve access with **Allow** when requested.
6. Wait for Kernel to confirm authorization, then verify the result below.

Keep the existing connection for a routine reauthorization. Reinstalling the package or creating another connection is not a required step in this flow.

## Verify the result

Check the Salesforce org and authorized user after the flow completes. Your Salesforce administrator can review **Setup › Connected Apps OAuth Usage**. If Kernel displays a different username, ask Kernel Support to check the mismatch before relying on the displayed name.

After switching users, test a small, agreed operation that changes a value and inspect the affected record's **Last Modified By** and **Last Modified Date** in Salesforce. Check the actual destination, such as Kernel Account or Account. A write to Kernel Account does not establish that the standard Account was updated.

Review any Record Sync schedules inside Salesforce separately. Reauthorizing Kernel does not by itself verify the user running those scheduled jobs or the effect of your Salesforce flows and triggers.

## Troubleshoot authorization

| What you see                                      | What to check                                                                                                                                                                                   |
| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Password-reset email is missing                   | Check the email on the Salesforce user. If Kernel owns that mailbox, coordinate password setup with Kernel.                                                                                     |
| Salesforce or SSO signs in as the wrong person    | Close the authorization window, log out of the Salesforce session for that org, and start Reauthorize again. Confirm the username before approving access.                                      |
| Login succeeds but Kernel keeps loading           | Check the Salesforce window for a consent screen or error. Salesforce login and Kernel's completed OAuth authorization are separate steps. Record the attempt time and exact error for support. |
| Salesforce rejects the user or application        | Ask your Salesforce administrator to review the user's active status, login restrictions, and the Kernel Connected App's access policy.                                                         |
| Authorization succeeds but a workflow fails       | Check the operation's object, field, and record permissions, plus validation rules and automation. Reauthorization does not grant those permissions.                                            |
| The connection later requires authorization again | Ask your administrator to review token revocation, user changes, and the Connected App's refresh-token policy. Authorization is subject to your Salesforce policies.                            |

Salesforce's [Connected App OAuth policy guide](https://help.salesforce.com/s/articleView?id=sf.connected_app_manage_oauth.htm\&language=en_US\&type=5) explains permitted users, IP restrictions, and refresh-token expiration. Your administrator should review these policies against your organization's requirements.

If the problem continues, send Kernel Support the org ID, environment, intended Salesforce username, installed package version and namespace, attempt time with timezone, and the exact error. Include the relevant job or record ID where applicable. Exclude passwords, API keys, tokens, and full authorization URLs.
