A Loyalty Management Consultant recently created a new analytics app, but users cannot access the app. Which two statement correctly describes hot to…

To grant users access to a CRM Analytics application like "Analytics for Loyalty," two distinct permissions must be assigned at the user level. First, the user requires a permission set license, specifically "CRM Analytics Plus User," which enables the core functionality of the analytics platform for that user. Second, the user must be assigned a permission set, such as "Analytics for Loyalty User" or "Analytics for Loyalty Manager." This permission set grants the specific permissions needed to access the components of the Analytics for Loyalty app, including its datasets, lenses, and dashboards. Both are required for the user to see and use the app.

A. Assign user access to the analytics for Loyalty role.

Roles in Salesforce primarily define a user's position in the hierarchy, which controls record-level access visibility, not access to applications like CRM Analytics.

D. Assign the user the analytics profile for analytics for Loyalty.

While profiles can grant permissions, the standard and best practice for managing access to CRM Analytics is through permission sets and permission set licenses for more granular and scalable control.

1. Salesforce Help, Set Up the Analytics for Loyalty App: "To give users access to the Analytics for Loyalty app, assign them the CRM Analytics Plus permission set license. Then assign them the Analytics for Loyalty Manager or Analytics for Loyalty User permission set." This directly confirms the necessity of both the permission set license (Option B) and the specific permission sets (Option C).

2. Salesforce Help, Assign Permission Sets for CRM Analytics: "To enable CRM Analytics functionality for users in your org, first assign each user a permission set license. Then, to grant users the permissions they need, assign them one of the standard permission sets: CRM Analytics Plus Admin or CRM Analytics Plus User." This document establishes the foundational requirement of assigning a permission set license before assigning a permission set for access.