Got 2 minutes? We'd love your feedback to help us improve our documentation.

Permissions for the Natterbox Data Connector (API User)

Prev Next

The Natterbox Data Connector, also known as the API user, is the single Salesforce account that Natterbox uses to read from and write to your org. This guide explains the licence, profile permissions and org settings that account needs in order to work correctly.

⚠️

Important: Deactivating this account, or removing any of the permissions below, stops data being queried from and stored to Salesforce. This affects call logging, call pop, wrap-up and all reporting data.

Licence and org requirements

  • Salesforce edition: Enterprise, Unlimited or Performance.

  • API access: must be enabled for your org, and the account must operate within the API request limits set by Salesforce.

  • Licence type: a dedicated Salesforce Integration licence is recommended, as it carries no UI seat cost. A full Salesforce licence also works but is more expensive. Chatter Free and Community licences will not work, because they cannot make API calls.

For most orgs, the simplest and most reliable option is to assign the System Administrator profile to the Data Connector user. This account must have full read/write access to all objects, with View All Custom Settings and API Enabled switched on. If you would rather build a dedicated integration user with a tailored profile, use the permission reference below.

Required profile permissions

If you are not using the System Administrator profile, the account needs at least the permissions below. These must be set directly on the profile — several of them cannot be granted through a permission set.

Permission

Why it is needed

API Enabled

Without it, Natterbox cannot connect at all and all data sync stops.

Activities (create/edit)

A call log task is created on the relevant record after each call.

View All Data and Modify All Data

Only required in private-sharing orgs, so the account can update Contact, Account, Lead, Case and Opportunity records owned by other users.

Customize Application

Needed to write Natterbox configuration held in protected custom settings.

Set Audit Fields upon Record Creation, and Update Records with Inactive Owners

Needed for wrap-up where the record owner has since been deactivated.

View All Custom Settings

Read access to the CTI server address, feature flags and licence information.

Permission sets

Assign both of the following permission sets to the Data Connector user. Together they cover all object-level access required, so no individual object configuration is needed:

  • NBVC_Administrator_PermissionSet

  • NBVC_BasicUser_PermissionSet