Blog

/

How To Set Up A Salesforce Integration User: How-To Guide & Best Practices

How To Set Up A Salesforce Integration User: How-To Guide & Best Practices

Not every integration with Salesforce provides you with the ability to restrict access to records in your Salesforce org. Some integrations have an “all or nothing” approach to the synchronization of data. This document will guide you through the process of creating and configuring a Salesforce Integration User. It addresses best practices and data privacy concerns related to using a perennial Integration User with the Salesforce Integration User License and the Salesforce API Only System Integrations Profile and shows you how to configure Salesforce to only allow certain records to sync with the connected integration.

How To Set Up A Salesforce Integration User: How-To Guide & Best Practices

How to Set Up a Dedicated Integration User in Salesforce

Creating a dedicated Salesforce Integration User is one of the most effective ways to manage third-party integrations securely and at scale. Whether you're integrating with tools like HubSpot, Marketo, or any other platform, a custom Salesforce integration user allows you to apply fine-grained permissions, protect sensitive data, and maintain better audit controls.

In this guide, we’ll walk you through the steps for setting up a Salesforce integration user, covering key considerations such as permission set management, field-level security, and record-level access through sharing rules.

Why Use a Dedicated Salesforce Integration User?

Many third-party tools require broad access to your Salesforce org to function correctly. Without careful setup, these integrations can unintentionally expose sensitive records or fields. By using a Salesforce integration user with limited permissions, you gain full control over what the integration can see or change—boosting data privacy and security.

Additionally:

  • Salesforce provides five free Integration User Licenses
  • Separate users improve troubleshooting and monitoring
  • Dedicated users prevent sync disruptions due to employee attrition

Step 1: Create a New Salesforce Integration User

  1. Log in to Salesforce as an Admin.
  2. Go to: Setup > Users > New User
  3. Fill in the fields:
    • First Name: (Optional)
    • Last Name: e.g. "HubSpot Integration"
    • Email: A dedicated email for this integration
    • Username: Must be unique (e.g., hubspot-integration@yourdomain.com)
    • Role: Choose or create a role such as "Integration User"
    • User License: Salesforce Integration
    • Profile: Salesforce API Only – System Integrations
  4. Click "Save".

Assign the API Integration License

  • On the user detail page, go to Permission Set License Assignments
  • Click "Edit Assignments", then enable Salesforce API Integration
  • Click Save

Step 1: Create a New Integration User

  1. Log in to Salesforce as an administrator.
  2. Go to Setup > Users > New User.
  3. Fill in the required fields:
    • First Name:[Optional]
    • Last Name: [Something meaningful like the Name of the Integration]
    • Email: [a dedicated email address for the integration user]
    • Username: [a unique username for the integration user]
    • Role: [assign an appropriate role, e.g., Integration User]
    • User License: Salesforce Integration
    • Profile: Salesforce API Only System Integrations
    • Click "Save" to create the new Integration User.
  4. Assign the "Salesforce API Integration" permission set license to the newly created user by clicking on the "Permission Set Group Assignments [x]" link at the top of the user detail page.
    • Click "Edit Assignments" in the “Permission Set License Assignments” section of the page
    • Scroll down to the "Salesforce API Integration" permission set license
    • Check the box in the "Enabled" column
    • Scroll to the top/bottom of the page and click save

Ready to Measure the Full Funnel and Grow?

Schedule a call

⚙️ Step 2: Restrict Access to Sensitive Fields

Controlling field-level access is essential to prevent exposing sensitive information during data sync.

To configure field-level security:

  1. Go to Setup > Object Manager > Select Object (e.g., Account, Contact)
  2. Click Fields & Relationships > Select a field
  3. Click "Set Field-Level Security"
  4. Uncheck the "Visible" box for the Integration User profile
  5. Click Save
  6. Repeat for all fields that should remain hidden from the integration

Step 3: Create a Custom Permission Set (Optional)

Since Salesforce is retiring profile-based permissions in Spring ’26, managing access via Permission Sets is best practice.

To create a custom permission set:

  1. Go to Setup > Users > Permission Sets > New Permission Set
  2. Name it something like "[Integration Name| Access" (e.g. HubSpot Sync Access)
  3. Save the permission set
  4. Add Object and Field Permissions based on integration requirements
  5. Add System Permissions if needed (e.g., API access, metadata editing)
  6. Assign the permission set to the Integration User under Manage Assignments > Add Assignments > Select user > Assign

Step 4: Create a Public Group for the Integration User

Salesforce Sharing Rules don’t apply to individual users, so you’ll need to create a Public Group that includes your integration user.

  1. Go to Setup > Users > Public Groups
  2. Click "New Group", give it a label (e.g., "HubSpot Integration Group")
  3. Save the group
  4. Click Manage Members > Add the Integration User

Step 5: Configure Sharing Rules for Record-Level Access

To limit which records an integration can access, use a combination of checkbox fields and sharing rules.

Create a Custom Field:

  1. Go to the desired Object (e.g., Account)
  2. Add a custom Checkbox field, e.g., "Send to HubSpot"
  3. Set the checkbox to TRUE only for records you want to sync.


Set Org-Wide Defaults:

  1. Go to Setup > Security > Sharing Settings
  2. For each object (e.g., Account, Contact), set Org-Wide Defaults to Private

Create Sharing Rules:

  1. Scroll to the object’s section (e.g., Account Sharing Rules)
  2. Click New Sharing Rule
  3. Set:
    • Rule Type: Based on Criteria
    • Criteria: Send to [Integration] = TRUE
    • Share With: The Public Group from Step 4
    • Access Level: Read/Write
  4. Save

Repeat this process for each object relevant to your integration.

Now, the Integration User will only have access to Account records where the "Send to [Integration]" checkbox is checked.

Additional Resources

Need Help Configuring Your Integration User?

At Candybox, we help RevOps and Salesforce admins set up secure, scalable integration users tailored to your tech stack. Whether you're connecting HubSpot, Marketo, Segment, or other platforms, we can help optimize your sync architecture, reduce risk, and maintain system performance.

👉 Reach out to us here if you'd like help setting up or auditing your Salesforce integration users.

Candybox

Candybox Team

RevOps, Salesforce & HubSpot experts

Candybox designs and runs the Salesforce, HubSpot and AI systems behind fast-growing B2B SaaS companies.

Related

I like that Candybox is not afraid to push back for the good of their customers.
Claudio Cocivera
Sr. Manager Business Systems & Processes
Staffbase logo
Merger migration, no major bugs
6 months
Candybox took a personalised approach to our business; they didn’t build an out of the box solution; they tailored it to our needs with industry knowledge and best practices.
Arran Cruickshanks
Commercial Director
Sleek logo
Adoption in week 1
90%+
They are true thought partners and don't require a structured list of requirements. I gave them a high level set of objectives and they were able to translate that into tactical technical updates.
Chiraag Kapoor
Principal
It felt like I walked into a fully-functioning system.
Kimberly DelSignore
Kimberly DelSignore
RevOps Lead
Omni Analytics logo
How Omni scaled RevOps and built a high-impact data architecture with Candybox.
to a live CPQ (vs. 9 months)
2–3 months
Now, we actually work methodically and have a process.
Keith Jones
Keith Jones
Leader of GTM Systems
MURAL logo

Frequently asked questions

Straight answers to what B2B SaaS teams ask us most. Don't see yours? Just ask us.

Why is RevOps important for scaling companies?

When should a SaaS company hire its first RevOps role?

What’s the difference between RevOps, Sales Ops, and Marketing Ops?

What types of companies do you typically work with?

What is RevOps in SaaS?

What CRMs do you work with?

Can Candybox handle both strategy and implementation?