Help center Access and connected tools Prepare Salesforce API access for Supportbench: permissions, credentials and compatibility checks Updated Wednesday, October 28, 2026 · Marc Staine Supportbench needs more than a Salesforce username to synchronize customer and support records. The Salesforce organization must provide API access, the integration user must be allowed to use it, and that user must be able to read or write the specific objects and fields you configure. The authentication method must also be compatible with both products. Use this procedure before changing production synchronization or assuming that an API Enabled checkbox fixes every connection error. At a glanceFor: Salesforce administrators and Supportbench administrators preparing or troubleshooting a connection. Applies to: Supportbench Core.Start here: Salesforce Setup; then Supportbench Settings → Integrations → Salesforce Separate the four prerequisites · Choose and identify the integration user · Assign API Enabled through a permission set · Check the data permissions for the selected directions · Confirm the current connector’s authentication method · Verify in Supportbench without starting a broad import · Interpret common failures Separate the four prerequisites PrerequisiteWhat a successful check establishesWhat it does not establishOrganization API availabilityYour Salesforce edition and purchased capabilities provide API access.That a particular user or app may use it.API Enabled permissionThe chosen integration user has the relevant API permission.Access to every Account, Contact, product, asset, Case or Task.Object, field and record accessThe user can perform the configured operation on the intended records.That the connector can authenticate with the organization’s allowed method.Compatible app and authentication policyThe current Core connector can use the issued credentials under the organization’s policy.That every mapping or synchronization direction is correct.Salesforce API availability depends on edition and subscription. Have your Salesforce administrator verify your organization against Salesforce’s current API prerequisites instead of assuming every plan includes it. Provider requirements reviewed on 28 October 2026. Choose and identify the integration user Identify the Salesforce user whose credentials Supportbench will use. Permission changes must apply to that user, not merely to the administrator configuring the integration. A dedicated, appropriately licensed integration identity can make ownership and rotation clearer; this is an operational recommendation, not a requirement that every organization use the same license or profile.Record the intended Salesforce organization and whether it is Production or Sandbox.Confirm the user is active and permitted to access the required records.Choose the minimum read and write capabilities needed for the configured synchronization directions.Assign an owner for credential rotation and for changes to the user’s permissions or employment status.Keep credentials in your approved administrative process; never publish them in documentation or paste them into shared troubleshooting notes. Assign API Enabled through a permission set In Salesforce Setup, use the search to find Permission Sets. Open the appropriate existing permission set or have the administrator create one that matches your integration-access policy.Open System Permissions and edit the permission list. Enable API Enabled if your organization and license support it. Save the change.Assign the permission set to the actual integration user. If it was already assigned, verify that the effective permission now includes API access.Review the user’s effective access and any organization restrictions. If the permission is unavailable, ask the Salesforce administrator to check edition, license and policy rather than substituting a broad administrator profile.Salesforce manages these permissions through profiles and permission sets; use your organization’s established least-privilege process. See Salesforce user permissions and API security and access. Check the data permissions for the selected directions Configured Supportbench taskSalesforce access to verifyImport CompaniesRead access to the intended Accounts, mapped fields and records allowed by sharing.Import ContactsRead access to Contacts and their relevant Account relationships.Export ContactsThe create/update access and field permissions required by the enabled export behavior.Import products or company assetsRead access to the configured Product2 and Asset objects, mapped fields and relationships.Export cases and activitiesRequired Case and Task access, allowed values and integration custom fields.Synchronize a configured custom data tableAccess to the exact custom object API name, fields and operations in its mapping.Test one representative record. A user may be allowed to call the API but unable to read an Account owned by another team, update a protected field or supply a required picklist value. Fix the specific permission or mapping; do not grant broad access simply because a synchronization report contains one error. Confirm the current connector’s authentication method The current Core Salesforce connector uses username-password authentication with connected-app consumer credentials. Its fields are Consumer key, Consumer secret, Salesforce username, and Password and security token. The final field expects the password immediately followed by the security token. Salesforce’s requirements for a token depend on the login network and policy; obtain the appropriate value from the integration user’s authorized administration process.Salesforce now restricts new connected-app creation, and username-password flow is blocked by default for organizations created from Summer ’23 onward. Existing compatible apps and organization policies must be evaluated explicitly. The current Supportbench editor does not implement an alternative interactive OAuth, JWT or client-credentials procedure, so a token from one of those flows is not interchangeable.If your organization blocks this methodStop the setup and request a supported compatibility review from your Salesforce administrator and Supportbench Support. The existence of an “allow” setting is not a recommendation to disable an organization’s security restriction. Do not follow older instructions that promise a new connected app can always be created or authorized in a few clicks.Consult Salesforce’s username-password flow documentation, connected-app creation requirements, and authorization-flow restrictions. These provider requirements are separate from the Supportbench field labels. Verify in Supportbench without starting a broad import Return to Settings → Integrations → Salesforce. Check the environment and integration username before entering the compatible credentials.Select Test connection. It tests current form values without saving them. Capture a sanitized failure message if authentication is rejected.If the connection succeeds, save only the intended configuration. Review object directions and mappings before selecting Synchronize now.Verify a representative record and the expected direction after processing. Do not select Resynchronize all merely to test whether credentials are correct.Record the confirmed integration user, permission owner, tested objects and credential-rotation process without recording the secret values in the documentation. Interpret common failures FailureInvestigateAPI access unavailableOrganization edition/add-on availability and the integration user’s effective API Enabled permission.Login or authorization rejectedWrong environment or username, stale password/token, incompatible app credentials or a blocked authentication flow.Authentication succeeds but an object is inaccessibleObject permissions, field-level access and record sharing for the integration user.Some updates failRequired fields, data types, picklist values, validation rules or missing write permission.The connection broke after account maintenanceCredential rotation, user deactivation, app-policy changes or a removed permission set.When opening a support request, separate authentication failure from record-access or mapping failure. Provide the object and operation, approximate time and sanitized provider error. Never include the password, security token or consumer secret. Continue learning Plan and verify Salesforce synchronizationConfigure Salesforce connection, objects and mappings Was this article helpful? Yes No Thank you for your feedback.