sf-connected.jpg

Integration user

Nektar accesses your Salesforce organization through a designated Salesforce user, which we call the Integration User.

We recommend creating a dedicated Salesforce user account (a service account) to serve as the Nektar integration user, as this gives fine control over what data Nektar can access. If this is not possible, you may use a shared user account for all tools to access Salesforce, or use your own Salesforce user account as the Nektar integration user.

Your Salesforce administrator should provision an integration user on Salesforce before you can set Nektar up. It is also a good idea for the designated Nektar administrator in your organization to have the credentials for the integration user.

Permissions

The specific records and fields Nektar accesses may be controlled by configuring a Salesforce profile with access to only the appropriate records and assigning the Nektar integration user to that profile.

The permissions required for this profile are:

Permission Purpose
Modify All Data create and modify all Salesforce records it can access (e.g. add and update contacts and activities)
Modify Metadata Through Metadata API Functions create and modify custom fields for storing useful Nektar data.
Customize Application control field-level security for Nektar custom fields
Manage Profiles and Permission Sets grant other users visibility to the data in Nektar custom fields.
API access allow programmatic access

Reduced privilege alternatives

Connection

The Salesforce account you sign into while creating your Nektar organization automatically becomes your connected integration user.

You may connect a different integration user in the Connection section of Salesforce integration settings:

OAuth scopes

Sync