Lesson 20 of 22 · All lessons

Section 8 · User Setup · 7% of exam

8.1 User Accounts, Licenses, and Activation

3 min read Updated Nov 19, 2026

Exam objective

Differentiate baseline permissions from additive access and explain how roles relate to record visibility.

  • Provisioning begins with a request.
  • Scenario: A new sales coordinator needs to work with Leads, Accounts, Contacts, and Opportunities and view a team dashboard.

Official references: https://help.salesforce.com/s/articleView?id=platform.users.htm&language=en_US&type=5 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_overview.htm&language=en_US&type=5

Core concepts

A profile provides a user’s baseline settings and permissions. It can include object and field permissions, app access, login restrictions, and other settings. Permission sets add specific permissions without requiring an entirely different profile. Permission set groups can bundle permission sets for a job function. This model supports a consistent baseline with targeted additions, though administrators should still review the total effective access.

Roles serve a different purpose. A role hierarchy can influence which records users can access through management relationships. A role is not a complete permission bundle and does not grant object or field access by itself. A user may have permission to read Accounts but see only some Account records because of sharing. Another user may have role-based visibility but still lack the object permission required to open the object.

Example: Two service agents have the same baseline profile. One agent temporarily handles billing cases, so a narrowly defined permission set grants access to the billing workflow fields and app. The agent’s role may reflect their team manager and influence record visibility. This arrangement is usually easier to review than creating many nearly identical profiles, but permission sets should be named and assigned carefully.

When a user reports missing access, review the assigned profile and permission sets, then identify which capability is missing. Is the app not visible? Is the object inaccessible? Is a field hidden? Is the record inaccessible? Is edit permission missing? Avoid assigning a broad administrator profile as a diagnostic shortcut. Compare the user with a colleague who has the intended job function and inspect only the relevant differences.

Access can be cumulative: multiple permission assignments may grant more than the administrator intended. Therefore, role changes and project completion should trigger a review. If an employee no longer handles a function, remove the extra permission set and verify that no other assignment still grants the same access. Document why sensitive permissions are needed.

Names and exact access features can change across Salesforce releases. Use current Salesforce Help for configuration details; the exam tests foundational distinctions.

Profile = baseline; permission set = additional capability; role = hierarchy context for record visibility. Use this mental model to eliminate mismatched answers.

Extra concept

Extra concept: Permission set groups can simplify job-based assignments, and muting permission sets can adjust permissions within a group in supported scenarios. These are administrative design tools beyond the basic Foundations depth.

Key takeaways

  • A profile provides a user’s baseline settings and permissions.

Check your knowledge

Answer exam-style User Setup questions with answers and explanations.

Practice User Setup
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Foundations simulator: same number of questions, same time limit.

Get Complete Access