What is the difference between a permission-set license and a permission set in CRM Analytics?

A permission-set license (the CRM Analytics Plus PSL) entitles a user to the feature — it is the seat you paid for. A permission set then authorizes what the user can actually do. You need both: the license alone grants no capabilities, and a permission set will not stick without the license.

What does the Manage Analytics permission do, and who should have it?

Manage Analytics is the master permission that grants essentially full control over CRM Analytics — creating and editing apps, dashboards, datasets, connections, and dataflows. Reserve it for administrators and platform owners, and give everyday users scoped permission sets instead.

What is the Analytics Integration User and why must it not be deleted?

The Integration User is the system account CRM Analytics authenticates as to read core Salesforce objects and sync them into datasets. It is the engine behind every data sync, so deleting or deactivating it breaks data ingestion across the entire org.

Why might a custom field come across blank in a dataset?

The Integration User has access to most standard objects and fields by default, but not to custom objects and fields. If you sync a custom field without granting the Integration User read access to it, the sync warns or fails and the field lands empty.

How does locale affect the data brought into CRM Analytics?

The Integration User's locale drives the language of the data values, such as Opportunity Stage picklist values. This is separate from labels and headers, which follow the running user and the company language. A wrong Integration User locale can bring in picklist values in an unexpected language.

What are the two jobs of the Security User?

First, it previews data in Data Prep recipes — the 'view as' sample rows while you build datasets. Second, it reads fields on the User object at query time so security predicates can enforce row-level security. Like the Integration User, it must never be deleted.

Explain row-level security and security predicates in simple terms.

Row-level security filters the rows of a dataset per user, so two people opening the same dashboard can see different amounts of data. It is driven by a security predicate — a filter rule evaluated at query time against the running user's User-object fields, such as their id or region.

Where do you enable CRM Analytics features, and what is the golden rule for beta features?

In Setup, search Analytics and open Settings, which holds per-environment feature toggles like output connections and SQL support. Because each sandbox and production has its own settings, always enable new or beta features in a sandbox and prove them before switching them on in production.

Setup & Provisioning: Interview Questions

Interview questions

8 common questions with model answers — rehearse each one aloud.

1
What is the difference between a permission-set license and a permission set in CRM Analytics?
A
A permission-set license (the CRM Analytics Plus PSL) entitles a user to the feature — it is the seat you paid for. A permission set then authorizes what the user can actually do. You need both: the license alone grants no capabilities, and a permission set will not stick without the license.
2
What does the Manage Analytics permission do, and who should have it?
A
Manage Analytics is the master permission that grants essentially full control over CRM Analytics — creating and editing apps, dashboards, datasets, connections, and dataflows. Reserve it for administrators and platform owners, and give everyday users scoped permission sets instead.
3
What is the Analytics Integration User and why must it not be deleted?
A
The Integration User is the system account CRM Analytics authenticates as to read core Salesforce objects and sync them into datasets. It is the engine behind every data sync, so deleting or deactivating it breaks data ingestion across the entire org.
4
Why might a custom field come across blank in a dataset?
A
The Integration User has access to most standard objects and fields by default, but not to custom objects and fields. If you sync a custom field without granting the Integration User read access to it, the sync warns or fails and the field lands empty.
5
How does locale affect the data brought into CRM Analytics?
A
The Integration User's locale drives the language of the data values, such as Opportunity Stage picklist values. This is separate from labels and headers, which follow the running user and the company language. A wrong Integration User locale can bring in picklist values in an unexpected language.
6
What are the two jobs of the Security User?
A
First, it previews data in Data Prep recipes — the 'view as' sample rows while you build datasets. Second, it reads fields on the User object at query time so security predicates can enforce row-level security. Like the Integration User, it must never be deleted.
7
Explain row-level security and security predicates in simple terms.
A
Row-level security filters the rows of a dataset per user, so two people opening the same dashboard can see different amounts of data. It is driven by a security predicate — a filter rule evaluated at query time against the running user's User-object fields, such as their id or region.
8
Where do you enable CRM Analytics features, and what is the golden rule for beta features?
A
In Setup, search Analytics and open Settings, which holds per-environment feature toggles like output connections and SQL support. Because each sandbox and production has its own settings, always enable new or beta features in a sandbox and prove them before switching them on in production.

Discussion

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