Set Up Analytics App Licenses and Permissions
- Breeze through setting up licenses and permissions for Analytics apps.
- Describe the difference between permission set licenses and permission sets.
- Assign user permissions so your team can access apps.
- Set up access permissions to sensitive Salesforce data.
(Not) For Admins Only
Let’s get you going in your adopted role as analytics guru for DTC Electronics. Today, you’ve been bombarded with requests to set up Sales Analytics. So, let’s learn how to do that quickly, and maybe have a little fun in the process.
After ensuring that your Analytics app is enabled, we’ll give other people access to it, and then we’ll determine what they’re allowed to do. Remember—the same basic techniques apply to any prebuilt Analytics app. Ready?
You Plus One!
The org already has two active users. Yes—one is you! The other is Laura Garza, one of DTC’s sales managers. The account you’re using right now, set up specifically for this trail, has complete admin privileges for that org. Your life would be so simple if that was the only account you needed. But in real life you need to meet the needs of many users, with various roles, each requiring various levels of access. Trailhead imitates life: Laura Garza has been bugging you about Sales Analytics. Her CEO is about to fly in for a meeting, and although Laura has access to Analytics, she wants access to the Sales Analytics app as well to show how her team is doing this quarter.
So, to get her going, you’re going to:
- Give her permission to use Sales Analytics.
- Create a set of permissions and assign it to her so she has the access she needs to get ready for her meeting.
Not everyone can handle the awesome power of having access to all things Analytics. Let's create a permission set specifically for sales managers—just enough to do what they need. You don’t want the sales manager and other users to be able to do everything you can do as an admin. Analytics lets you control security at a very granular level for every Analytics app. So you’ll create that permission set to make sure she has access to just what she needs to do her job.
So, now let’s see what Laura has permission to do in Analytics. To do that, you first need to make sure it’s enabled.
Permission Set Licenses and Permission Sets: They’re Different
The term "permission set license" is quite a mouthful and it’s really easy to confuse with "permission set". But those are two different things, and you must keep them distinct when you set up Analytics. To start with, for the sake of brevity, we’re going to call "permission set license" by its acronym, PSL. (For those of you who aren’t into the whole brevity thing, you can still call them "permission set licenses" whenever you like.)
Looking at these two things in the context of the setup process can help you keep them straight:
The first part of the process involves creating a permission set, and associating it with a PSL. Before you can select any PSL for Analytics, you must have purchased an Analytics license. You can purchase either the Analytics Platform license or a license for a specific Analytics app—or both.
Next, you add some permissions to the permissions set, from those available in the PSL. Then you can then assign that permission set to users, in this case, Laura.
Clear as mud? Here’s an analogy that might make things a little clearer. A PSL is like a passport. It grants you the right to travel, but you can't visit the great land of Analytics without the right visa. A permission set is like a visa. You can get a three-day tourist visa, a work visa, and so on, each of which allows you to do certain things. To do everything you want to do, you need both a passport and a visa, which is why you need to assign each user at least one PSL and one permission set.
Let’s Get Granular! Create a Permission Set
Create Permission Sets
Since this permission set is for Laura, and other sales managers who just need to see a Analytics app (and not create or customize it), type View Analytics App in the Label field. Adding the label automatically creates the API name as well, which we’ll keep.
- In the Setup menu, under Administration, click Users, then Permission Sets and then click New.
- Enter View Analytics App in the Label field. This automatically creates the API name as well, which we’ll keep.
- From the License drop-down menu, select the license to associate with this permission set. In this case, select the Sales Analytics Apps permission set license. This step is equivalent to the passport in our analogy. If you select a specific permission set license, any user assigned to the permission set is auto-assigned the permission set license. If you leave the default of --None--, you must manually assign the permission set license to users before you can add them to the new permission set. Of course, auto-assignment mean less for you to do!
- Click Save. The Permission Set Overview page shows the new permission set. Now add user permissions to the set.
Some Thoughts About Permissions
When you created the permission set, you also specified the PSL to associate with it ("Sales Analytics Apps"). This PSL makes a specific set of permissions available to assign—but they haven't been granted yet! You need to figure out which permissions are appropriate, and then assign them to the permission set you plan to assign to users.
So, essentially you’re going to create a subset that's right for sales managers like Laura. You won't give her all these permissions. There are more Analytics permissions for other license types, but these are the ones available for the apps license.
We’ll order them slightly differently here so you can see how they’re related:
- Use Analytics Templated Apps. This permission is for users who need access to any Analytics apps included with the Einstein Analytics platform license (which is called Einstein Analytics Growth). This includes Sales Analytics and a variety of other apps you can see when you select Create and open the template picker.
- Manage Analytics Templated Apps. This is an admin-level permission that lets you create, share, and delete apps. You should be careful about assigning this to users like Laura, who probably won’t need to create apps.
- Edit Analytics Dataflows. Another admin-level permission. You use this to do app customizations that involve changing app data. As such, it’s for advanced admins who are comfortable with editing a bit of JSON. Don’t worry if you don’t know what JSON is.
- Download Analytics Data. Download screenshots and data in tabular format through the Analytics user interface.
- Edit Dataset Recipes. This allows you to customize the data in your app with recipes, an advanced Analytics data integration feature you won’t be using in this Trailhead module.
We will only assign some of these permissions.
Add Permissions to the New Permission Set
- On the permission set overview page look for the System section. Under that, click System Permissions. If you closed the permission set overview page, go to Setup, click Users—>Permission Sets, and click View Analytics App to reopen it.
- Click the Edit button.
- Since we’re creating a permission set called View Analytics App just for Laura (and users like her who just need to view apps), select the check box for the permission that enables that level of access: Use Analytics Templated Apps.
- Click Save.
Wow—you’ve successfully created a permission set that lets Laura view the Sales Analytics app. Only one last task to wrap everything up.
At the Finish Line! Assign Permission Sets
- In Setup, click Permission Sets.
- Click the permission set you just created, View Analytics App.
- Click Manage Assignments.
- Click Add Assignments.
- Select the checkbox for our insistent Sales Manager, Laura Garza, and click Assign.
- Click Done.
Wrapping Up, and What’s Next
You’re done—way to go! You’ve assigned a PSL to another user, created a new permission set, added permissions to that set, and assigned the set to the user. That’s a lot of steps, but it’s all about security, security, security!
The same basic process applies to other app and users, even though you did all this using Sales Analytics. The differences are the permission set license (PSL) you assign, and the specific permissions you add to permission sets. Each app requires that you assign users the unique PSL for that app. And a different type of user—say an admin, or a power user—would require that you add other permissions to give them access to the app features they need.
For now, pat yourself on the back, and take a few well-deserved deep breaths. You’re well on your way to becoming an Analytics guru!