Section 8 · User Setup · 7% of exam
8.2 Profiles, Permission Sets, and Role Context
Exam objective
Manage user changes safely and distinguish personal preferences from administrative permission changes.
- Roles serve a different purpose.
- Example: Two service agents have the same baseline profile.
Official references: https://help.salesforce.com/s/articleView?id=sf.admin_userprofiles.htm&language=en_US&type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&language=en_US&type=5 https://help.salesforce.com/s/articleView?id=platform.users.htm&language=en_US&type=5
Core concepts
User access changes over time. Onboarding, transfers, leave, and offboarding all require a controlled process. When a user changes teams, review license needs, profile, permission sets, role, groups, and ownership of important work. When a user leaves, deactivate access promptly through approved policy, transfer records or scheduled responsibilities as appropriate, and remove access to connected systems where required.
Personal preferences affect how a user experiences Salesforce, not the underlying authorization model. A user can have personal settings such as language, locale, time zone, or notification preferences where supported. These settings can affect dates, times, and communication. They should not be confused with organization settings or permissions. For example, changing a time zone may alter how event times display; it does not grant access to other users’ events. Scenario: An employee moves from sales to customer support. Before changing access, determine which historical records and open Opportunities the employee must retain, which Cases they need, and whether their new manager should see their work. Then adjust the role and permission assignments under the organization’s process and transfer ownership where needed. Test the result by confirming both the new work access and the removal of obsolete access. Access reviews should be risk-based and repeatable. Managers can confirm whether users still need sensitive capabilities. Administrators can identify stale assignments, inactive users, excessive privileges, and records owned by former employees. Keep a clear approval trail. An audit trail can help understand configuration changes, but it does not by itself establish that every access grant is appropriate.
Users should protect credentials and approved authentication methods, report suspicious activity, and avoid sharing accounts. Shared logins make it difficult to attribute actions, enforce least privilege, and investigate incidents. Follow the organization’s policies for MFA, password management, single sign-on, and device security; exact settings depend on the org and current Salesforce product capabilities.
Deactivation affects login but does not automatically resolve every operational dependency, such as record ownership, scheduled jobs, or external integrations. Follow the full offboarding checklist.
For a preference request, use personal settings. For an access request, review the permission model and obtain the appropriate authorization.
Extra concept
Extra concept: Login history and administrative audit tools can support investigations. Treat them as evidence sources with defined retention and access controls, not as a substitute for a documented security response process.
Key takeaways
- User access changes over time.
- Personal preferences affect how a user experiences Salesforce, not the underlying authorization model.
