Universal Containers has decided to implement Salesforce Einstein Analytics for a subset of its users. How should the administrator enable users with permissions to use Einstein Analytics features?

While creating permission sets for specific Analytics permissions is a valid step, creating 'a new permission set for *each type* of Einstein Analytics permissions' might lead to unnecessary complexity, and a single comprehensive permission set or permission set group is often more efficient for enabling a user subset.

Permission sets are assigned directly to users or to Permission Set Groups, not added to existing user profiles, which define baseline permissions.

Salesforce Einstein Analytics (now CRM Analytics) features are enabled for users by assigning specific permission sets. While permissions are directly assigned to users, administrators often manage access for a 'subset of users' by creating a logical grouping (which might be referred to as a 'sharing group' in this context, such as a Public Group) and then ensuring the appropriate CRM Analytics permission sets are assigned to the members of this group.

Creating new profiles for a subset of users to grant access to specific features like Einstein Analytics is generally discouraged; permission sets are the recommended method for extending user permissions without creating profile sprawl.