> ## Documentation Index
> Fetch the complete documentation index at: https://support.parker.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Salesforce

> Connect your Salesforce login, choose whether Parker's changes are live, and find the admin controls for your workspace's Salesforce connection.

Everything about Salesforce lives on one page: **Settings** > **Connections** > **Salesforce**. Each person connects their own Salesforce login there. Admins also see an **Admin** section with workspace-wide controls.

## Before you begin

* You need a Salesforce login for your org.
* To use the **Admin** section, you need the **admin** role in Parker.

## Open the Salesforce page

Go to **Settings** > **Connections**, then select the **Salesforce** row.

The page has three cards: **Connection**, **How Parker works in Salesforce**, and, for admins, **Admin**. **Advanced** sits below them.

![Connection card showing the Salesforce account as Connected, the Salesforce MCP row, and the Email to Salesforce row with Set up.](https://mintcdn.com/fieldko/SNnUZRlfUC06vUK1/images/admin/connect-salesforce-connection.png?fit=max\&auto=format\&n=SNnUZRlfUC06vUK1\&q=85\&s=745fac3d980ac3209962fede46b4639d)

## What's in the Connection card?

* **Salesforce account**: shows **Connected** and "Connected as" your Salesforce username. Select **Details** to see more, or **Disconnect** to remove your login.
* **Salesforce MCP**: how many Salesforce MCP servers are active in your org. Select **View servers** to see them.
* **Email to Salesforce**: BCC your outbound emails to Salesforce so each one is logged to your activity. Select **Set up** to add your address.

### Check it worked

The **Salesforce account** row shows **Connected**. On **Settings** > **Connections**, the Salesforce row also shows **Connected**.

## What can Parker see and change?

Parker works as the person who's asking, under that person's own Salesforce permissions. Your Salesforce profiles, field-level security, and sharing rules still apply. So two people asking the same question can get different answers.

![Card with Agent mode set to Live, the Writes row listing objects with Manage, and the Sync row with View.](https://mintcdn.com/fieldko/SNnUZRlfUC06vUK1/images/admin/connect-salesforce-how-parker-works.png?fit=max\&auto=format\&n=SNnUZRlfUC06vUK1\&q=85\&s=aaa9f03b19c09936c1253c74ff886ed0)

### Test and Live mode

Under **How Parker works in Salesforce**, each person chooses an **Agent mode**: **Test** or **Live**. In **Live**, write tools commit changes to Salesforce, as you, under your own permissions. Every write is audited.

> [!WARNING]
>
> **Check before Parker changes Salesforce.**
>
> * **Creating** a record shows a card with **Confirm** and **Reject**. Nothing is written until you select **Confirm**.
> * **Updating** an existing record has no card. If you've told Parker exactly what to change, it makes the change straight away in **Live** mode.
>
> See [How Parker acts on your behalf](/get-started/how-parker-acts).

### Bulk updates

On the **Writes** row, select **Manage**. Choose which objects allow bulk updates, and set **Approval required above (rows)**. Above that row count, a bulk change needs a second person's approval. A blank threshold means no threshold. Select **Save writes** to keep your changes.

## Admin controls

![Admin card with the Connected App row marked Configured, the Salesforce MCP servers switch, and the Org-wide test mode switch.](https://mintcdn.com/fieldko/SNnUZRlfUC06vUK1/images/admin/connect-salesforce-admin.png?fit=max\&auto=format\&n=SNnUZRlfUC06vUK1\&q=85\&s=fc6e5c2d2bfee264ef5a90d03be9d26b)

* **Connected App**: shows **Packaged connector** when Parker supplies the credentials, so there's no Consumer Key to maintain. Select **Manage** to see the connection details. There you can also enter an **Experience Cloud site URL** so community users can connect through your site's own login.
* **Use Salesforce MCP servers for this connector**: when on, Parker reaches MCP servers that are active in your Salesforce org, for people who've connected Salesforce MCP. When off, Parker uses the standard Salesforce API only.
* **Org-wide test mode**: forces everyone in your org into **Test** mode, whatever their own setting. Use it for rollout, regulated work, or an incident.

### What's under Advanced?

Select **Advanced** for profiles, org limits, schema cache, API governance, tuning, and audit logs. For example:

* **Schema cache**: select **Refresh schema** after a Salesforce admin adds, renames, or removes fields.
* **Schema change review queue**: Salesforce metadata changes that might affect your reports. Select **Open** to accept or dismiss them.
* **Org limits**: how much of your daily API requests and data storage is used.
* **Recent Salesforce writes**: the newest write events from your org. Field names are recorded; values aren't.

## Troubleshooting

> **Parker's changes aren't reaching Salesforce**
>
> Check that person's **Agent mode**, and whether an admin turned on **Org-wide test mode**. Only **Live** commits changes to Salesforce.

> **Parker can't see a record or field**
>
> Parker sees what the asking person sees. Check that person's access in Salesforce.

> **Parker doesn't know about a new field**
>
> Go to **Advanced** and select **Refresh schema**.

## Related

> **[Connections and apps](/admin/connections-and-apps)**
>
> Everything else Parker connects to.

> **[Ask about Salesforce data](/chat/salesforce-questions)**
>
> What your team can ask once connected.

> **[Update records](/chat/updating-records)**
>
> How Parker changes Salesforce, and how you confirm.

> **[Troubleshooting](/reference/troubleshooting)**
>
> More fixes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.