When you start working with Salesforce Einstein Analytics it was easy to give permissions to the users. But after a while, you will end up with two roles, where one can do everything, and the other can't do anything. So this article will help you understand the granularity of each permission and how to strike a balance between right permission and the right access.
So this quick walkthrough on the permissions will help you define the roles and responsibilities that you want to assemble.
Wave System Permissions
- View Wave Analytics on Community pages
- Use WA Template Apps
- Use Wave Analytics
- Upload Data to WA
- Trend Report Data in WA
- Manage WA Template Apps
- Manage Wave Analytics
- Edit Wave Analytics Dflow
- Download Data from WA
- Create WA Apps
- Create and Edit Wave Analytics Dashboards
- Access SAQL Editor
- Access Salesforce Template Apps (SalesCloud, Service Cloud & Event Monitoring Apps)
To make it simple I will split these permissions into three different categories
-
L1 : Permission that gives the basic access
-
L2 : Permissions that works like the add-ons
-
NO : Restricted Permissions that you should not assaign without a proper reason
So when you have to add access to wave for a particular user, start with these questions
What basic role do I have to give (refer to L1)?
Does he need any add-ons listed (refer to L2)?
Does he need any of the restricted permissions?
My thumb rule is to always begin with the bare minimum permissions. Here you can find a sample of how you should classify these permissions to gain full control.
More Info
