Start tracking your progress
Trailhead Home
Trailhead Home

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.
  • Understand both the custom and basic processes for assigning permissions to users.

Enable Analytics

The Developer Edition (DE) org provided for this trail takes care of this step for you. Analytics is already enabled, so you don’t need to do anything. Your company’s production org displays an Enable Analytics button the first time you open Analytics from the app menu. You click the button to enable Analytics for your team when you begin the setup process. Since that’s already taken care of in the DE org, you can move to the next step.

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. After you purchase an Analytics license, you can follow either a basic or custom process for assigning permissions. The basic process lets you assign a default permission set to users. It lets you get the job done quickly, but gives you less control.

The custom process takes more work but gives you fine-grained control over the permissions you assign. It involves these steps:

  1. Assign Analytics permission set licenses to your users.
  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 both the basic and custom processes for both users. 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.

If you follow the custom process, you first assign a permission set license to users. The PSL enables a set of user permissions in your org, but doesn’t assign them without you doing something first.

That “something” is to create a permission set. Select the permissions you want to assign from the specific permissions enabled by the PSL, and add them to the permission set. You then assign that permission set to users.

The basic process makes things much simpler: All you do is assign one of the prebuilt permission sets that come with an Analytics platform license. (With basic permission assignment, you don’t have to be concerned about permission set licenses.)

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.

User Permissions Enabled by 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
Note

Note

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

Custom vs. Basic Permission Set Assignment

How do you know whether to follow the custom or basic setup processes? It’s a matter of control: If you need fine-grained control over what users can and can’t do with Analytics, use custom. If you instead want to provide full permissions for users to access Analytics features, use basic.

Most of the time, the basic option provides what you need. An Analytics Platform license includes two default permission sets, Einstein Analytics Platform User and Einstein Analytics Platform Admin. The user permission set includes a single permission: Use Analytics. The admin permission set includes the broad range of user permissions needed to build an Analytics solution.

Use the custom option when you need to carefully consider the level of Analytics access required by members of your team. Perhaps some users need more than the simple permission to use Analytics. They might need to import data, or create dashboards and apps. Or perhaps others need a more limited set of permissions than those granted by the default admin permission set. Remember, Analytics dashboards, lenses, and datasets can contain sensitive information, and you may want to put some time thinking about which users can see what.

Let’s take a quick look at how both processes work, starting with custom.

Note

Note

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 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 check next to 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.

What if Laura or other users needed additional permissions? Here’s where you could take care of that. In your browser, search for analytics in the Permission Sets page. For most browsers, use the Command-F key combo, and enter analytics. Scroll through the page to see all the highlighted Analytics permissions you could add to the Analytics Trailhead Explorer.

Or, you could create a new permission set.

  1. Under Setup, click Permission Sets, then New.
  2. Enter Example Permset in the label field.
  3. Select the Analytics Platform permission set license from the License menu, and click Save.
  4. Click System Permissions.

You can see all the possible Analytics user permissions. You could click Edit, choose the ones you want to add to the example permission set, then save it to create a custom permission set. You could then assign it to users.

You won’t do that here, since we don’t need to enable any new users. But this gives you the idea of how to use a custom permission set to give you granular control over a user’s access to Analytics. Now take a quick look at the basic process.

Use Basic Permission Sets

You should still be in the Users area of Setup.

  1. Click Users.
  2. Click your username.
  3. Just under your name, click Permission Set Assignments.
  4. At the top of the page, under Permission Set Assignments, you can see that you’ve already been assigned a permission set. Click Edit Assignments.
  5. At the top of the list, you can see the default permission sets that ship with an Analytics Platform license, Einstein Analytics Platform Admin, and Einstein Analytics Platform Admin.
  6. Have a look at the permissions included in each set. In the Setup panel at far left, right-click Permission Sets and open the link in a new window.
  7. Click Einstein Analytics Platform Admin, then System Permissions to see the user permissions included in that permission set. Then click back twice and do the same thing for the Einstein Analytics Platform User permission set.
  8. Now that you know what permissions they contain, select one of them and click the Add arrow to add it to the Enabled Permission Sets list.

If you clicked Save, you’d have assigned yourself that permission set along with its permissions. That also automatically assigns you a permission set license, saving you that step. You could follow the same process to assign a default permission set to other users in your org. Much simpler, right? And you still have some control over what users get access to which Analytics features.

Analytics gives you choice over how to assign permissions to members of your team. You can enable other features to enhance their Analytics experience. We’ll look at how to do that next.

retargeting