Permission Set Overview
Permission sets allow managed packages the ability to create a set of permissions to extend to an individual user of Salesforce. Instead of granularly tracking permissions, it is a way to enable full control and access in a single action.
Admin and Agent Permission Sets
The Guided Selling by Revenue.io managed package introduces two permission sets that must be assigned to all users who will utilize the tool:
Sequence Admin
The Sequence Admin permission set should be applied to users who will manage users in Guided Selling, and create Actions and build Sequences for Guided Selling users.
Sequence Agent
The Sequence Agent permission set is limited compared to Sequence Admin. These users will have access to Engage, adding or removing their Leads from a Sequence, and completing Sequence Actions. They will not be able to build or manage Sequences or Actions.
Note: Adding an object to a Sequence requires the user to have Edit access on the Lead/Contact. If the user does not have edit permission Revenue.io will be unable to associate the Lead/Contact to a Sequence.
Object Permissions for the Sequence Admin and Sequence Agent Permission Set
|
Object |
Total Fields |
Sequence Admin |
Sequence Agent |
|
12 |
Read, Create, Edit, Delete, View All, Modify All |
Read, View All |
|
|
Email Action Events |
-- |
Read, Create |
Read, Create |
|
Emails |
-- |
Read, Create |
Read, Create |
|
Email Templates |
7 |
Read, Create, Edit, Delete, View All, Modify All |
Read, Create, Edit |
|
Folders |
5 |
Read, Create, Edit, Delete, View All, Modify All |
-- |
|
Loggers |
14 |
Read, Create, Edit, Delete, View All, Modify All |
Read, Create, Edit, Delete, View All, Modify All |
|
Participant Actions |
72 |
Read, Create, Edit, Delete, View All, Modify All |
Read, Create, Edit, Delete, View All, Modify All |
|
Participant Sequence History |
11 |
Read, Create, Edit, Delete, View All, Modify All |
Read, Create, Edit, Delete, View All, Modify All |
|
Sequence Action Events |
-- |
No Access |
Read, Create |
|
Sequence Actions |
17 |
Read, Create, Edit, Delete, View All, Modify All |
Read, View All |
|
Sequence Email Actions |
11 |
Read, Create, Edit, Delete, View All, Modify All |
Read, Create, Edit, Delete, View All, Modify All |
|
Sequence History Events |
-- |
Read, Create |
Read, Create |
|
Sequence Object Associations |
6 |
Read, Create, Edit, Delete, View All, Modify All |
Read, Create, Edit, Delete, View All, Modify All |
|
15 |
Read, Create, Edit, Delete, View All, Modify All |
Read, View All |
|
|
5 |
Read, Create, Edit, Delete, View All, Modify All |
Read, View All |
|
|
User Settings |
6 |
Read, Create, Edit, Delete, View All, Modify All |
Read, Create, Edit, Delete, View All, Modify All |
Guided Selling Delegation
A third permission set, Guided Selling Delegation, enables a user to trigger the addition of a record to a Sequence if the record matches the Sequence entrance criteria.
This permission set is intended for non-Guided Selling users-- i.e., the user is not completing actions or building Sequences. This permission set is best applied to third-party users such as Lean Data or Hubspot to ensure fresh leads are added to a Sequence immediately.
The Guided Selling Delegation permission set should never be applied to a user that has the Sequence Agent or Sequence Admin permission set. Doing so will prevent any records owned by the user from progressing through sequences.
Permission Set User Assignments vs Group Assignment
For Guided Selling to function properly, these Permission Sets must be assigned directly to the user in Salesforce. The application checks for assignment of these permission sets to determine if/when certain triggers should run.
When Permission Sets are assigned via Group, the permission set doesn't exist for the individual and cannot be queried. As a result, the application will not function.