Configure Role-Based Permissions
When you invite people from other teams like Demand Gen and Customer Success to use SlapFive, you'll want to configure which functions and data they should see. This section explains how to do it.
SlapFive enables you to define Roles, assign Users to Roles, and determine which menu options and data that Users in each Role have permission to see and edit.
SlapFive comes pre-configured with these two Roles:
Admin: this is the default role for new Users you invite to SlapFive, and is used for members of your core team who need access to all SlapFive modules and data.
Viewer: this role is automatically assigned to any users who access SlapFive content and features from within the SlapFive Salesforce App.
SlapFive enables you to define these two levels of permissions for each Role:
Access: What level of access do Users have to each Entity on the SlapFive menu? Sample use cases:
Filters: What filters should be applied to the data that Users can see when accessing each Entity? If you define multiple filters for different fields for the same entity, AND logic is applied so that the records the user can see must meet all filter criteria. Sample use cases:
Define and configure a new Role
Create a new Role for each department or function from which you want to invite people to access SlapFive and who's members share the same permissions. To create a new Role, follow these steps:
Log into SlapFive and go to Admin menu > Roles.
Click the Add Role button, enter the name for the new Role, click the OK button and you will see a list of Entities which correspond to SlapFive menu options.
Under the Access column, each Entity has a drop-down field with different access levels. Select which access level to grant Users in this Role from these choices:
Under the Filters column, each Entity has a (+) button that allows you to apply filters to the data that Users in this Role can see. To add a new filter, select values for each of these fields and then click the Save button:
Click the Save button to save the Role.
Here is an example of a Marketing Role that has been defined with Access and Filter permissions:
Last updated