Assign Permissions

Learning Objectives

After completing this unit, you’ll be able to:

  • Describe the purpose of Analytics permission set licenses and how to assign them.
  • View user permissions to determine what access a user has to Analytics features.

Enable Analytics

If you’re using the org provided for this trail, we’ve made it easy for you; Analytics is already enabled. You don’t need to do anything. In your company’s production org, you see a large stylish Enable Analytics button the first time you open Analytics from the app menu.

Give Users Permission to Use Analytics

This is where we cover the nitty-gritty of setting up user access to Analytics. As the Salesforce admin for DTC, you ensure that all users have appropriate levels of access. For example, some users need view-only permissions, while others need permission to update dataflows or create apps.

Your users don’t see the Analytics app until you assign them the right permission. Here’s what you do.

  1. Purchase an Analytics license, then assign Analytics permission set licenses to your users. You can’t assign Analytics permissions to a user who doesn’t have a Analytics permission set license.
  2. Create a permission set that contains all the permissions your user needs, then assign the permission set to the user.
Your Analytics-enabled DE org has two active users, you and Laura Garza. Let’s follow this process to check the level of access that each of you has to Analytics. But first, let’s talk about permission set licenses, permission sets, and how to remember which does what.

Permission Set Licenses and Permission Sets: They're Different

”Permission set license” (PSL) is not only a mouthful, it’s also easy to confuse with “permission set”. But they are two different things; keep them distinct when you set up Analytics.

First you assign a PSL to users.

Next, you select from the specific permissions enabled by the PSL. The permissions you select become part of a permission set. You can then assign that permission set to users.

If You Remember Nothing Else, Remember This

Here’s an analogy that can make things clear. 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 3-day tourist visa, a work visa, or a student visa. Each visa type lets you do certain things. Just like a traveler needs both a passport and a visa, your Analytics users need at least one PSL and a permission set.

Assigning an Analytics Permission Set License

The PSL determines which permissions you can assign to a user. You can only assign permissions that are included in that user’s PSL.

Your DE org includes the Analytics Platform (and/or (or Einstein Analytics Plus) PSL, which lets you assign a number of user permissions, including the following:

  • Create and Edit Analytics Dashboards
  • Create Analytics Apps
  • Edit Analytics Dataflows
  • Manage Analytics
  • Upload External Data to Analytics
  • Use Analytics


Analytics apps (such as Sales Analytics) have their own PSLs and associated user permissions. We cover apps in a later unit.

Who Can Do What

Just as you do for other Salesforce features, carefully consider how much Analytics access users need. Analytics dashboards, lenses, and datasets can contain sensitive information, so spend some time thinking about which users can see what.

In this module, you need user permissions that are available in the Analytics Platform (or Einstein Analytics Plus) PSLs. Let’s makes sure the right license is assigned to you.



The names and labels described here may not match exactly the ones you see in your Analytics-enabled Developer Edition org. However, the principles and techniques we take you through apply to any org you use.

  1. From Setup, enter Users in the Quick Find box, then select Users.
  2. Click your username.
  3. The user details page appears. Scroll down to the Permission Set License Assignments section. Be sure to view the PSL section, not the Permission Set Assignments section. They’re easy to confuse with each other! The PSL section listing PSLs assigned to user.
  4. It looks like the license assignments are fine. You have the Analytics Platform (or Einstein Analytics Plus) permission set license. You may have other licenses in addition to these.
  5. If you’re curious, click Edit Assignments to see what other licenses are available. Don’t make any changes, though. You need your current PSL so you can complete challenges in this module.

    Now let’s check on the other active user in this org, Laura Garza.

  6. Repeat steps one to five, but this time click Laura Garza’s username, not yours.
  7. View Laura’s PSL. It looks something like this: The PSL section listing PSL assigned to Laura.

    Laura’s permission set license assignment is fine. But Laura isn’t an admin, so she has limited access to Analytics. The permission set associated with her PSL reflects her limited access. Let’s take a look.

  8. Scroll up Laura’s user page to the Permission Set Assignments section.
  9. Click the permission set assigned to Laura, Analytics Trailhead Explorer.The perm set assigned to Laura.
  10. In the permission set page, scroll down to the System section and click System Permissions. The System Permissions link on the Perm Set page.

The System Permission page has a long list of permissions, almost all of which are unselected. If you scroll down, down, down, you see a lonesome little checkmark on the Use Analytics permission.

Use Wave Analytics perm is checked.

As the description indicates, this is a view-only permission, so all is correct. Laura doesn’t have admin rights.

The combination of a PSL and associated permission sets gives you granular control over a user’s access to Analytics. It’s all about security, security, security!