CRMA Academy

Before You Start: Provisioning Users for CRM Analytics

Setup is the admin's first job in CRM Analytics: make each person a Salesforce user, then assign the permission-set license and permission set that unlock analytics.

Before You Start: Provisioning Users

Before anyone builds a single dataset or dashboard, an administrator has to open the door. Setup is the very first step in any CRM Analytics (formerly Tableau CRM) project, and it happens entirely on the admin side of the house. This section walks through everything that has to be true before a user can log in and see the Analytics Studio.

The golden rule is simple: everyone who uses CRM Analytics must first be a Salesforce user. CRM Analytics is not a separate product with its own logins — it lives inside your Salesforce org and rides on top of the platform's identity, sharing, and security model. If a person cannot log into Salesforce, they cannot use CRM Analytics.

Users usually already exist

In practice you rarely create brand-new users just for analytics. The sales reps, managers, and analysts you want to enable are almost always existing Salesforce users already working in Sales Cloud or Service Cloud every day. Your job is usually not to create them from scratch but to grant them the extra access that turns on analytics.

That extra access comes in two layers, and the distinction matters for the rest of this section:

Permission-set license (PSL)

The CRM Analytics Plus license. It entitles the user to the feature — think of it as buying the seat.

Permission set

One or more permission sets that actually authorize what the user can do, from admin-level control to a narrow, read-only scope.

You need both. The license entitles the person; the permission set switches on the specific capabilities. We cover each in depth in the next two lessons.

The provisioning flow

Here is the end-to-end path an administrator follows to get one person up and running. Keep this sequence in mind — every later lesson slots into it.

  1. 1

    Create or confirm the Salesforce user

    Make sure the person exists as an active Salesforce user with a login. Most of the time they already do, so you just confirm the account.

  2. 2

    Assign the permission-set license

    Grant the CRM Analytics Plus permission-set license (PSL) on the user record. This entitles them to the analytics feature.

  3. 3

    Assign the permission set

    Attach one or more permission sets that authorize what they can do — Manage Analytics for full admin control, or a scoped set for everyday users.

  4. 4

    Verify access

    Have the user open the App Launcher and confirm the Analytics Studio loads and the expected apps and datasets are visible.

Provisioning is a two-part grant: license, then permission set. If a user has the license but no permission set, they are entitled but still cannot do anything. If they have a permission set but no license, the assignment simply will not stick. Always check both.

Why get this right first

Setup mistakes are the number-one reason a rollout stalls before it even starts. A user who cannot see the Studio, a sync that fails on a custom object, or a dashboard that shows the wrong rows almost always traces back to something skipped here. Getting provisioning right — the correct license and a thoughtfully scoped permission set — means the rest of your CRM Analytics work stands on solid ground.

In the next lesson we open up the first of those two layers: the licenses and permission sets that entitle and authorize your users.

Discussion

No comments yet — be the first to start the discussion.

Interview Questions

Rehearse the most common beginner CRM Analytics (Tableau CRM) interview questions — datasets, dashboards, recipes, Einstein Discovery, and the adoption pillars — with model answers.

Licenses & Permissions

Understand the CRM Analytics Plus permission-set license versus permission sets, and how Manage Analytics and scoped permission sets grant the right access to each user.