Authentication
PLEASE NOTE: SFDC Editions with API Access include: Enterprise, Unlimited, Developer, and Performance. Any licenses that do not have this edition cannot communicate to external services via API.
When using the Salesforce connector for the first time you will need to create a new authentication:
You will then have to select the necesary Scopes for your authentication. This will configure the access level your Tray workflow will have to your Salesforce account:
Note that for standard use, you will always need to tick the API scope
You will then be prompted to enter the credentials of the Salesforce user you will be authenticating with.
This user must be set up with the correct permissions in the Salesforce Admin UI to ensure that they will be able to access all the available connector operations.
Granting Access to Tray.io in SalesforceCopy
Encountering issues while authenticating with Salesforce, especially during the integration of a third-party app like Tray.io, may result from Salesforce blocking the application.
Salesforce's default settings or specific organizational security policies can automatically block third-party apps that administrators have not pre-authorized. This is a standard precaution to prevent unauthorized access.
Steps to Unblock an App in Salesforce:
Log in to your Salesforce account.
Navigate to Platform Tools from the Home menu.
Under Platform Tools, select 'Apps', then choose 'Connected Apps'.
Proceed to 'Connected Apps OAuth Usage'.
In the list of apps, locate 'Tray.io'.
In the Actions column, check the status of Tray.io.
If Tray.io is blocked, an option to 'Unblock' will appear.
Click 'Unblock' to grant Tray.io access.
This action removes the restriction, allowing Tray.io to interact with Salesforce as intended.
Following these steps should effectively resolve any access issues related to app blockages in Salesforce.
Correct setup of User PermissionsCopy
Managing AccessCopy
The Salesforce connector gives you full access to all of your Salesforce account data such as your leads, contacts, custom objects/fields, workflow rules, outbound messages and more.
The way you handle who has access to this data is through the use of Salesforce Users, Profiles and Permission sets.
Your User will have access depending on their associated Profile permissions or Permission sets - in a read, write, create capacity; depending on whats required.
Be sure sure to note the following access rules before you confirm who has what level of access to which data sets. More information on Profiles and Permission sets can be found below.
Every User must be assigned a Profile.
There can only be one Profile per User.
The User you are creating an authentication for MUST have access to all the object types you want them to manipulate.
Currently the Salesforce connector can only be used on the Enterprise Edition of Salesforce, and higher. You may use the Salesforce connector on Professional Edition, but ONLY if you've requested API access from your Salesforce account manager. However, you will not be able to use instant WebHooks on the Professional Edition.
ProfilesCopy
In Salesforce you can allocate a user to a pre-set Profile or you can create your own Custom Profile.
The available Profiles for a User will depend on the type of License that User has. More information on this can be found below.
Note that the Contract Manager Profile comes as standard and is suited to the access level required by both the Salesforce Trigger and Connector.
Profile vs Custom ProfileCopy
Pre-set Profiles are included as part of your Salesforce account.
However please note that the kinds of pre-set Profiles that are available to you will depend on the type of License that a User has.
For example a Salesforce Platform-licensed User can only have a Standard Platform User Profile.
While a Salesforce-licensed User can have multiple Profiles. Including Contract Manager and System Administrator which will give them comprehensive 'super-user' access to all functions and objects within Salesforce.
Custom Profiles allows users to design their own original Profile based on use case specific requirements.
Please see License Types for more details.
Adapting ProfilesCopy
The Contract Manager Profile comes as standard and has a lot of the permissions needed in order to use the Trigger or Connector effectively.
You can see this by checking out the Standard Object Permissions section within the Contract Manager Profile setup page:
Despite having a lot of access there may be more areas that you would like your User to have access to.
A good approach would be to clone the Contract Manager profile and then edit the permissions while bearing in mind the following:
Profile Setup sectionsCopy
Here are the key sections within any Profile Setup page you should be aware of:
Standard Object Permissions
Set basic read and write access to objects such as contracts, leads, accounts etc.
Administrative Permissions
Where key permissions can be set.
For example API Enabled must be ticked or your authentication will not work.
General User Permissions
Allow extra functionality that cannot be granted purely through object-level permissions.
For example Activate Contracts must be ticked for it to be possible to activate a contract. The Edit permission on Contracts and Orders is not enough to allow contract activation
(you can test activating contracts in Tray with the Update Record operation for the Contract record type - setting the Status field to 'Activated').
This applies to several other options within this section such as Manage Cases and Activate Orders.
Helpful ResourcesCopy
TooltipsCopy
The Salesforce UI has tooltips which tell you what object settings are also required for certain permissions:
Object permissionsCopy
This User profile permission descriptions article is a great source of reference for explaining more about controlling what Users can do within your Salesforce Organization via User Profile permissions.
Permission SetsCopy
In Salesforce it is possible to use Permission Sets to extend users' functional access, without altering their Profiles. This means that the level of access within the Profile itself will not change.
The access level of other Users also using the same Profile type will remain the same. Only your selected User will have increased permissions. Permission sets are like access level 'add-ons'.
Permission Set exampleCopy
For example say you have a User that has a Read Only profile. Your User already has an allocated Profile with permissions based on that particular Profile group.
In order to extend the access rights for this particular User (without affecting the Profile grouping and thereby the rest of the Users who are also utilising this Profile) you would need to create a Permission set.
You could create a Permission Set which has all the necessary access required and then assign the Permission Set to a particular user .
Specifying a licenseCopy
When you create a Permission Set you can also specify the License it is suppose to be used with:
