> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.getmasset.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.getmasset.com/_mcp/server.

# Salesforce

With the Masset for Salesforce integration, you can sync Salesforce records into Masset, associate shares and content rooms with the right CRM records, and write engagement activity back to Salesforce. It is designed for teams that want CRM context inside Masset while still honoring Salesforce-side access controls.

Using the Masset for Salesforce integration, you can:

1. **Search** synced Salesforce records from Masset when creating shares and content rooms.
2. **Associate** those shares to Salesforce records so engagement stays tied to the right CRM entity.
3. **Write engagement activity back** to Salesforce as either `Masset_Engagement__c` records or standard Salesforce Tasks.
4. **Sync Salesforce users** into Masset and link them to the right Masset users for attribution.
5. **Control sync behavior** by choosing which Salesforce object types are enabled and reviewing sync history from the integration settings page.

## Supported records

Masset can sync any queryable, layoutable Salesforce object with a `Name` field, including many standard objects and custom `__c` objects. Most teams start with Accounts, Contacts, and Opportunities, then enable additional object types as needed from the Salesforce integration's **Objects** tab.

## Salesforce features

The Salesforce integration is primarily a Masset-side workflow. After setup, sellers can search synced Salesforce records from Masset while creating shares or content rooms. When a record is selected, Masset stores the CRM association so downstream engagement can be tied back to the correct Salesforce record.

Admins can also choose where Masset engagement data lands in Salesforce. By default, Masset writes to the packaged `Masset_Engagement__c` custom object. If your team prefers to keep engagement activity on standard Salesforce records, you can instead write those events as Salesforce Tasks.

Salesforce users are synced automatically from the connected org. From the integration details page, admins can enable automatic email-based association or manually map Salesforce users to Masset users. That mapping ensures search, share attribution, and engagement write-back stay tied to the correct seller.

> **Note**
>
> Masset expects the Salesforce integration to expand over time. As functionality grows, Masset will continue to honor Salesforce visibility rules and Masset permissions when deciding what users can search, view, and associate.

## Installation

To install the Salesforce Integration, the installer should be both a Masset Admin and a Salesforce System Administrator. Before starting the org connection, Masset recommends deciding which Salesforce user will act as the dedicated integration user.

To launch the guided setup flow from Masset:

1. Log in to Masset.
2. Go to **Admin** > **Integrations**.
3. Click **Add Account**.
4. Select **Salesforce**.

Then complete the guided setup:

#### Install the Masset package in Salesforce

1. Click **Install in Salesforce** from the setup flow.
2. Log in to Salesforce as a System Administrator.
3. Choose **Install for Admins Only**.
4. Wait for Salesforce to confirm the install completed.
5. Verify that **Masset** appears under **Installed Packages** in Salesforce Setup.

The managed package adds the `Masset_Engagement__c` object, the `Masset Integration User` and `Masset Salesforce App User` permission sets, and the Masset Salesforce Foundation External Client App.

![](/_fern-files/_img/0e7717b72d17e9a76503d0730134e21c4bb29008bf05bd9c79102877660cfb18.webp)

#### Assign the integration user permission set

1. In Salesforce Setup, open **Users**.
2. Open the user that should act as the Masset integration user.
3. Click **Permission Set Assignments** > **Edit Assignments**.
4. Add **Masset Integration User** and save.

Masset recommends using a dedicated integration user so engagement writes do not break when a named employee leaves or changes roles.

#### Assign the app user permission set to your team

1. In Salesforce Setup, open **Permission Sets** > **Masset Salesforce App User**.
2. Click **Manage Assignments** > **Add Assignments**.
3. Select the Salesforce users who should be able to connect Masset to their Salesforce identity.
4. Save the assignment list.

This permission set allows each seller to authorize Masset to act on their behalf when their Masset and Salesforce identities are linked.

#### Connect your Salesforce org to Masset

1. Return to the Masset Salesforce setup flow.
2. Click **Connect Salesforce Org**.
3. Sign in as the integration user you configured earlier.
4. Review the requested access and click **Allow**.

This is the org-level OAuth handshake between Masset and Salesforce. It establishes trust using the External Client App installed with the package.

If Salesforce shows **This app isn't installed for your user**, confirm that the package install completed and that the integration user has the **Masset Integration User** permission set assigned.

#### Link Salesforce users to Masset

1. Open the Salesforce integration details page in Masset.
2. Review the synced Salesforce users.
3. Enable automatic email-based association, or manually link any users that do not auto-match.
4. Confirm every seller who should create or own CRM-linked shares is linked to the correct Salesforce user.

![](/_fern-files/_img/af481b33b154d2266bd2f7d8403798a447ad337f9805a441150a4c6f6967f01c.webp)

After the org connection is complete, open the Salesforce integration details page in Masset to choose which Salesforce object types to sync, trigger a manual sync if needed, review sync history, and manage user mappings.

## FAQ

### What OAuth scopes does the integration request?

The Masset for Salesforce integration requests the following OAuth scopes from Salesforce:

| Scope           | Description                                                                                                                                |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `api`           | Allows Masset to call Salesforce APIs to sync object metadata, sync records, sync users, and write engagement activity back to Salesforce. |
| `openid`        | Allows Masset to identify the connected Salesforce user and org during org connection and user linking.                                    |
| `refresh_token` | Allows Masset to maintain the connection and continue running scheduled syncs without requiring repeated re-authentication.                |

### What Salesforce data does Masset read?

Masset only reads the Salesforce data needed for sync, search, and attribution:

1. Org and user identity during OAuth connection, including org id, user id, email, and instance details.
2. `Id` and `Name` for any enabled Salesforce object types that you choose to sync.
3. Salesforce user records used for user linking: `Id`, `Email`, `FirstName`, `LastName`, and `IsActive`.
4. Record-access checks via Salesforce's `UserRecordAccess` model so Masset can honor Salesforce sharing rules when returning search results.

### What Masset data is written back to Salesforce?

Masset never uploads the raw asset file into Salesforce. When engagement write-back is enabled, Masset only writes event metadata such as the event type, event timestamp, Masset event id, associated Salesforce object type and record id, and the Masset content room id. If the target record name is already known to Masset, it may also be included for reporting convenience.

Depending on your chosen engagement target, that data is written either to:

1. the packaged `Masset_Engagement__c` custom object, or
2. a standard Salesforce Task on the associated record.

### Do users need to connect their own Salesforce account?

Admins can link users in two ways:

1. Enable automatic association by matching Salesforce and Masset users by email.
2. Manually map Salesforce users to Masset users from the **Users** tab in the Salesforce integration settings.

Users can also connect their own Salesforce account directly from Masset. When they do, searches run under that user's own Salesforce token. If they have only been admin-mapped, Masset still filters results using Salesforce's record-access checks so users only see records they can actually read.

### Can I limit what Masset syncs from Salesforce?

Yes. Admins choose which Salesforce object types are enabled for sync from the **Objects** tab in the Salesforce integration settings. Masset only syncs enabled object types, and only syncs the `Id` and `Name` fields for those records.

### What permissions does the integration user need if I use Salesforce Tasks as the engagement target?

If you switch the engagement target from `Masset_Engagement__c` to `Salesforce Task`, the integration user must have **Create**, **Read**, and **Edit** access on Salesforce Tasks.

### Where can I submit feedback?

If you have questions, feedback, or want help with setup, reach out to [support@getmasset.com](mailto:support@getmasset.com).