Fours

Install the Fours App

Install the Fours managed package from Salesforce AppExchange and establish a live, two-way connection between Salesforce and Fours.


Overview

By the end of this guide, you will have:

  • The Fours package installed in your Salesforce org
  • A dedicated Integration User set up for the connection
  • A live, verified two-way connection between Salesforce and Fours

You only need to complete this setup once.


Prerequisites

Make sure you have the following before you begin:


Step 1: Install the Fours package from AppExchange

This installs the Fours App into your Salesforce org.

  1. Go to the Suger listing on Salesforce AppExchange.
  2. Click Get it Now.
  3. Log in with your Salesforce Admin account when prompted.
  4. Choose where to install:
    • Select Production for your live org.
    • Select Sandbox if you are testing first.
  5. When asked who to install for, select one of the following:
    • Admins Only — recommended to start; you can expand access later.
    • All Users — installs for everyone immediately.
    • Specific Profiles — installs only for selected profiles.
  6. Click Install and wait for the confirmation email from Salesforce.

Step 2: Create a dedicated Integration User

The Integration User is a special Salesforce account that Fours uses to read and write data in your org. It is not a person — it is a service account.

Choose a license type

Pick the right license before creating the user.

License typeWhen to use
Salesforce Integration LicenseUse this in most cases. It is free and designed for API-only connections. The user cannot log in via the Salesforce UI.
Salesforce License (standard)Use this only if your field mapping involves Quote objects — either a standard Salesforce Quote or a CPQ Quote.

Create the user

  1. In Salesforce, click the Gear icon (⚙️) → Setup.
  2. In the Quick Find box, type Users and select Users.
  3. Click New User.
  4. Fill in the required fields:
    • Enter a recognizable name like Fours Integration.
    • Enter a valid email address — Salesforce will send an activation link here.
    • Set the License to whichever option you chose above.
  5. If you selected Salesforce Integration License, set the Profile to Salesforce API Only System Integrations.
  6. Click Save, then activate the user via the email Salesforce sends.

Assign permission sets to the Integration User

Permission sets control what data Fours can access in your org. You need to assign two things.

First — assign the Suger Integrator permission set

  1. Go to Setup → Permission Sets.
  2. Find and open the permission set that matches your license type:
    • Salesforce Integration License → assign Suger Integrator (Salesforce Integration License).
    • Salesforce License → assign Suger Integrator.
  3. Click Manage Assignments → Add Assignments → select your Integration User → Assign.

Second — create a custom permission set for object access

Fours also needs read access to standard Salesforce objects like Account, Contact, and Opportunity. Create a permission set for this manually.

  1. Go to Setup → Permission Sets → New.
  2. Name it something like Fours Integration Object Access.
  3. Set the license to match your Integration User:
    • Salesforce Integration License → select Salesforce API Integration (not “Salesforce Integration” — these are different).
    • Salesforce License → leave the license field as default.
  4. Inside the permission set, grant Read and View All access on:
    • Account
    • Contact
    • Opportunity
    • Any other objects or fields you plan to use in your Fours field mapping.
  5. If you are using standard Salesforce Quotes, also grant Read access on Product2, Pricebook2, and Quote.
  6. Save the permission set, then assign it to your Integration User using the same steps above.

Step 3: Configure Salesforce to talk to Fours

This step tells Salesforce where Fours is and how to authenticate with it. You do this from inside the Fours App in Salesforce.

  1. In Salesforce, click the App Launcher (the nine-dot grid icon in the top-left) and search for Suger.

  2. Open the Suger app and navigate to Settings.

  3. Fill in the following fields:

    FieldWhat to enter
    Organization IDYour Fours Org ID from Settings → Organization & Users.
    API Endpointhttps://api.suger.cloud
    API KeyYour Fours API Key from Settings → API Client.
  4. Click Save.


Step 4: Connect Fours to Salesforce

This step goes in the other direction — it authorizes Fours to read and write data in your Salesforce org using the Integration User you created in Step 2.

  1. Go to Fours Console → Settings → Integrations → Salesforce.
  2. Click Connect Now.
  3. Enter your Salesforce Subdomain — for example, acme.my.salesforce.com.
    • Find this in Salesforce at Setup → Company Settings → My Domain.
  4. If you are connecting to a Sandbox org, check the Sandbox checkbox.
  5. Click Create.
  6. Salesforce will prompt you to log in — sign in as the Integration User you created in Step 2, not your personal admin account.
  7. After logging in, return to Fours Console and click Verify to confirm the connection is live.

For more detail on the integration configuration and mapping options, see the Salesforce Integration Setup Guide. Which Fours objects are written into Salesforce, and how far back each one goes, is set on the integration’s Backfill To Salesforce Configuration tab — see Choose What Backfills to Salesforce.


Troubleshooting common issues

IssuePossible causeResolution
API Key authentication failsTrailing space in the API Key fieldDelete and re-enter the API Key, making sure there are no spaces before or after it.
“Not approved for access” error during OAuthIntegration User’s profile is not listed under Permitted Users in the Suger External Client AppGo to Setup → External Client App Manager → Suger → Policies and add the Integration User’s profile or permission set under Selected Profiles/Permission Sets.
Fours buttons not visible after connectionUser has not been assigned the correct Fours permission setGo to Setup → Permission Sets and assign the appropriate Fours permission set to the user.
Users can see buttons they should notExtra custom permissions were auto-enabled when the package was installedGo to the user’s profile → Custom Permissions and uncheck any Fours permissions that should not apply.
Connection works but data is not syncingIntegration User lacks Read/View All access on required objectsReview the custom object permission set you created in Step 2 and add any missing object or field access.
Salesforce Integration License user cannot log inThis is expected — the Salesforce Integration License is API-only by designUse a standard Salesforce License if your team needs the Integration User to log in via the UI.

Frequently Asked Questions

Do I need to reinstall the package every time Fours releases an update?

No. Fours pushes managed package updates automatically. You do not need to reinstall from AppExchange to get new features.

Can I use my personal Salesforce Admin account as the Integration User?

You can, but it is not recommended. If your account is deactivated, renamed, or its password changes, the Fours connection breaks. A dedicated Integration User keeps the connection stable regardless of staff changes.

Can I connect Fours to both a Production org and a Sandbox at the same time?

Yes. In Fours Console → Settings, you can add additional environments. Check the Sandbox checkbox when connecting a sandbox org.

What is the difference between the Suger Integrator permission set and the custom object permission set I created in Step 2?

The Suger Integrator permission set gives the Integration User access to Fours’ custom objects and features. The custom object permission set you created gives Fours access to your standard Salesforce objects like Account and Opportunity. Both are required.

What happens if I click “Connect Now” again on an existing connection?

It re-initiates the OAuth flow. Use this if the connection breaks, or if you have updated OAuth policy settings in Salesforce and need to reauthorize.

Spotted something wrong or out of date on this page? Tell us and we'll correct it.