Question

Difficulty: MediumUser Management and Provisioning

A Salesforce Administrator at a green energy enterprise needs to manually provision a new Regional Sales Director. The user requires base system access, proper record visibility through the role hierarchy, and specialized permissions granted via permission set groups. In which sequence should the administrator execute these setup steps to successfully provision the user?

  1. 1Select the appropriate User License and minimal base Profile on the new user creation form.
  2. 2Assign the user's position within the Role Hierarchy on the user edit page to ensure proper record access roll-up.
  3. 3Save the User record to establish the user account in the organization and trigger the setup notification email.
  4. 4Access the Permission Set Assignments related list on the saved User record to assign the required Permission Set Groups.

Answer

The correct administrative sequence is: 1) Select the User License and minimal base Profile on the user creation form, 2) Assign the Role within the Role Hierarchy on the user edit page, 3) Save the User record to create the active user account, and 4) Navigate to the saved User record's related lists to assign the required Permission Set Groups.
Provisioning a Salesforce user requires creating the record with mandatory fields (User License, Profile) and organizational attributes (Role) first. Saving the record creates the database entry and generates a User ID. Only after the record exists can an administrator access related lists on the User detail page to assign Permission Sets or Permission Set Groups for extra permissions.

Step-by-Step Solution

1
Configure required base user attributes on the creation page.
The user license and base profile are designated.
Salesforce mandates a license and profile selection upon user record initiation.
2
Assign the user's Role assignment on the creation page.
The user is positioned within the organizational Role Hierarchy.
Role selection is available on the main user edit interface prior to record creation.
3
Save the new User record.
The user record is committed to the database and assigned a unique User ID.
Saving the user record creates the underlying entity, making related child lists accessible.
4
Grant supplemental access via Permission Set Groups.
The user is granted extended capabilities beyond the base profile.
Permission Set Group assignments are managed via related lists on an existing, saved User detail page.

Key Concept

Sequential User Provisioning & Feature Access Management
Estimated Time:1m 30s
Rate this question