A Salesforce Administrator at a global logistics firm is tasked with onboarding a new Regional Dispatch Manager. The new user requires a standard user license, data visibility constrained by their geographic territory, specialized permission to manage custom Fleet records, and automated assignment to the Regional Incident Queue.
What is the correct sequential order of administrative steps required to provision this user while adhering to Salesforce security best practices?
- 1Create the new User record by populating mandatory fields, selecting the standard User License, and assigning a minimalist base Profile.
- 2Assign the user to their designated position within the Role Hierarchy.
- 3Assign the specialized Permission Set Group containing elevated object and field-level permissions for Fleet management.
- 4Add the newly active User to the Regional Incident Queue and associated Public Groups.
Answer
The correct order to provision the user is: 1) Create the User record with mandatory fields and baseline Profile, 2) Assign the user's Role in the Role Hierarchy, 3) Assign the specialized Permission Set Group, and 4) Add the User to the Regional Incident Queue and Public Groups.
The correct order follows Salesforce's logical dependency and security best practices: first creating the User record with required fields and a standard profile, then establishing baseline visibility via the Role Hierarchy, layering job-specific functional access using a Permission Set Group, and finally adding the user to queues and public groups for operational record routing.
Step-by-Step Solution
Key Concept
User Provisioning Workflow and Least Privilege Architecture
Estimated Time:2m 0s