Question

Difficulty: Very hardUser Management and Provisioning

A Salesforce Administrator at an enterprise organization is tasked with provisioning access for a newly hired Senior Financial Auditor who requires targeted access to confidential audit objects and executive reporting queues. Following security governance and Salesforce administrative best practices, in what order should the administrator execute the user provisioning workflow?

  1. 1Verify active User License availability under Company Information in Setup.
  2. 2Configure the base custom Profile establishing minimal organzational object permissions.
  3. 3Create the User record with required fields including Username, Email, User License, Profile, and Role.
  4. 4Assign the Financial Audit Permission Set Group to grant elevated system and field-level permissions.
  5. 5Add the user record to the Executive Audit Public Group to enable criteria-based record sharing rules.

Answer

The correct operational sequence begins with verifying license availability, defining the required base profile, creating the user record with mandatory fields, assigning supplemental permission set groups, and finally adding the active user to the public group for record sharing.
The correct order respects mandatory dependencies in Salesforce user administration: checking license availability precedes account generation; profile creation must occur prior to selection on the user form; user record creation instantiates the account; permission set groups provide targeted privilege expansion; and public group addition enables row-level sharing.

Step-by-Step Solution

1
Check Organization License Capacity
Confirmed an available Salesforce User License in Company Information.
User creation requires an unassigned active license of the targeted type.
2
Establish Base Profile Settings
Created or verified the minimal-privilege profile.
Profile selection is a required field on the User object during record save.
3
Instantiate the User Record
Saved the new user record with standard license and profile attributes.
A valid user ID is necessary prior to associating permission sets or public group memberships.
4
Assign Permission Set Group
Granted specialized financial audit permissions to the user.
Permission Set Groups build upon baseline profile permissions and must target instantiated users.
5
Add to Public Group
Included the user in the sharing hierarchy for audit records.
Public group assignment applies sharing rules to the active user account.

Key Concept

Salesforce User Provisioning Lifecycle and Access Layering
Rate this question