Section 2 · Security and Access · 20% of exam
2.2 Profiles, permission sets, delegated administration, and
Exam objective
Compare and contrast custom profiles, permission sets, and delegated administration; given a scenario, determine the implications of user authentication.
A profile supplies a user's baseline permissions and settings, while permission sets and permission set groups provide additive grants for job functions. A profile can establish object permissions, field permissions, app visibility, login hours, and other supported settings. Permission sets are a more flexible way to grant capabilities to a subset of users without creating many nearly identical profiles. A permission set group bundles permission sets for a persona; muting can remove permissions from the group combination but does not revoke an independent grant elsewhere. Effective access is the union of applicable grants and applicable restrictions.
Use profiles for a small number of stable baseline access patterns and permission sets for specialized or temporary responsibilities. For example, most support representatives can share one profile, while a smaller group receives a permission set for knowledge publishing or a feature license. When troubleshooting, inspect assignments from the user's profile, permission sets, groups, licenses, and role. A license constrains what can be granted; a permission set cannot grant a feature the user's license does not support. Avoid profile proliferation because it makes access reviews and change control harder.
Delegated administration lets selected non-administrator users perform limited administrative tasks for specified users or roles and, when configured, manage selected custom objects. It is useful when a regional operations lead should maintain users within a defined scope without receiving full Setup privileges. It is not a substitute for an admin profile if the task requires unrestricted configuration. Scope delegated groups and object permissions narrowly, and test whether the delegated administrator can manage only the intended population. Separate the ability to manage users from the ability to change security policy.
Authentication answers who the user is and whether the login is trusted; authorization answers what the authenticated user can do. Salesforce supports identity controls such as multifactor authentication, single sign-on, login policies, session settings, and trusted network restrictions. The appropriate design depends on whether users authenticate directly or through an identity provider, what assurance is required, and which connected applications are involved. Do not confuse a profile's login hours with a full identity policy. A successful authentication does not imply access to a record, and record sharing does not rescue a failed login.
When a login fails, classify the symptom before changing permissions. Check the username and login URL, user active status, password or identity-provider status, MFA enrollment, login hours, IP restrictions, session policy, and any certificate or SSO configuration involved. A user may authenticate to an identity provider and still be denied by Salesforce, or may log in but lack app or data access. Review login history and relevant identity-provider logs. Do not weaken MFA or network controls merely to clear one user's error; identify the specific failing control and use a narrow exception process if policy allows it.
Scenario method: list the actions the administrator needs to delegate, then map each one to user management, custom-object management, or setup access. Assign a least-privilege baseline, add capabilities with permission sets, and confirm license compatibility. For authentication questions, draw the path from user to identity provider to Salesforce session, then identify where the failure or policy decision occurs. Consider both user experience and security: a shared account reduces attribution and should not be used as a shortcut for a delegated task.
Exam focus: choose permission sets when a capability should be added for some users while keeping a small number of profiles. Identify delegated administration as scoped administration rather than broad Setup access. Separate login controls from record and object permissions. If the scenario asks why a user can log in but cannot perform an action, investigate authorization; if the user cannot establish a session, investigate authentication. For temporary access, plan assignment and timely removal rather than changing the default profile.
The exact authentication choices available to an org can depend on its configuration, licenses, and Salesforce release. Verify feature prerequisites in Salesforce Help before recommending a design.
Practical scenario:
A regional team lead should reset passwords and unlock users in a defined region but should not edit permission sets or sharing rules. Configure delegated administration for the intended group and scope; assign no broad system permissions. Give regional specialists any separate operational capability through permission sets. Test with a delegated account, verify the team lead cannot alter org security, and record a review date for the delegation.
Extra concept:
Session-based permission sets are an additional way to make selected permissions active only in a supported session context. They can reduce standing access for specific workflows, but the session activation mechanism and feature eligibility must be checked in current documentation. Treat temporary access as a lifecycle: grant, activate, audit, expire or remove.
Key takeaways
- Profiles establish baselines; permission sets add job-specific capabilities.
- Delegated administration is scoped and does not equal full Setup access.
- Authentication controls login; authorization controls Salesforce actions and data.
- Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.users_profiles.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.security_mfa.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&type=5
