Study guide

2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access

Salesforce Admin Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Administrator Orientation and Official Source Control

1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

2 Chapter 2: Configuration, Setup, User Management, and Org Controls

2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab

3 Chapter 3: Security, Access, Identity, and Sharing Model

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab

4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling

4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab

5 Chapter 5: Sales, Marketing, Service, and Support Applications

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab

6 Chapter 6: Data and Analytics Management

6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab

7 Chapter 7: Automation, Flow, Approval, and Operational Processes

7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab

8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange

8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab

9 Chapter 9: Agentforce for Platform Administrators

9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab

10 Chapter 10: Integrated Salesforce Admin Scenario Labs

10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy

11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy

11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review

2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access

Key Takeaways Explain This Topic AI

A user record combines identity, license assignment, role, profile, locale, time zone, manager, delegated administration, and operational fields that affect access and ownership.

The user license sets the outer boundary of available features, while profiles and permission sets determine what the user can do within that licensed boundary.

Permission sets and permission set groups are preferred for incremental access because they reduce profile sprawl and make exceptions easier to review.

Freezing, deactivating, password resets, login access grants, and ownership transfers are different admin actions with different operational consequences.

Last updated: October 2026

User records as access contracts

A Salesforce user record is more than a name and email address. It ties a person to a username, user license, profile, role, permission set assignments, locale, time zone, manager, delegated administration, default currency when applicable, and feature-specific settings. In Setup, the core path is Setup > Users > Users. From there, an admin can create users, freeze users, reset passwords, assign permission sets, inspect login history, and manage login access policies depending on org configuration.

The first judgment point is the user license. A license controls which platform features and object families are available at all. If a user has a license that does not support a feature, assigning a permission set cannot magically grant it. This matters in scenarios involving Salesforce Platform users, Experience Cloud users, add-on feature licenses, permission set licenses, and Agentforce-related capabilities. Before troubleshooting object permissions, confirm that the license can support the requested work.

Profiles still matter because every user has exactly one profile. The profile provides a baseline for object permissions, field permissions, tab visibility, app access, login hours, login IP ranges, page layout assignment, record type access, and system permissions depending on configuration. However, a profile should not become a custom snowflake for every small job variation. Too many profiles make audits painful and increase the chance that a future admin grants broad access just to fix one edge case.

Permission sets are the cleaner tool for incremental access. If a sales operations analyst needs report export ability for a project, a permission set can grant the specific permission without changing every user on the profile. Permission set groups help bundle related permissions for a job function, and muting permissions can suppress permissions inside a group where supported. Permission set licenses may also be required before some permissions become assignable. The exam trap is choosing a profile clone when a permission set would solve a narrow access requirement with less risk.

Access layering model

Layer What it answers Admin judgment

User license What Salesforce features can this user use at all Verify before troubleshooting permissions.

Profile What is the baseline for this user type Keep broad and role-aligned, not exception-heavy.

Permission set license Is an add-on permission family available Assign only when the feature is needed.

Permission set What extra capability does this person need Prefer for narrow or temporary access.

Permission set group What bundle fits this job function Use for repeatable jobs and easier review.

Role Where does the user sit in record visibility hierarchy Do not confuse role with profile.

Roles are frequently confused with profiles. A profile answers what the user can do. A role helps determine which records the user can see through the role hierarchy and sharing model. In a small org, some users may have no role, but in a sales or service hierarchy the role is often essential for manager visibility, forecasts, and territory-adjacent reporting. If a manager can run the app but cannot see subordinate records, the profile may be fine while the role or sharing model is wrong.

Usernames are globally unique across Salesforce, while emails are not the same thing as usernames. In sandbox and Developer Edition practice, this can surprise new admins who try to reuse an email-style username. A common pattern is to use a unique username that looks like an email address but includes an environment marker. The user email controls notifications and password reset delivery, so it still must be accurate for real users.

Deactivation is another scenario-heavy area. Salesforce doesn't let you delete users, because they own records, appear in history, and are part of audit trails; you deactivate them instead. Deactivation prevents login, and a deactivated user doesn't count against the org's available user licenses (billing changes only when you change the license count), but it can require reassignment of ownership, scheduled jobs, queues, workflow users, default lead owners, and integration ownership. Freezing a user prevents login quickly but does not replace deactivation or reclaim the license. Use freezing when immediate login prevention is needed while you prepare the full deactivation checklist.

Login access grants are for support and troubleshooting, not a workaround for permissions. A user may grant an admin or Salesforce support temporary access to inspect behavior as that user, depending on org settings. Admins should use this capability with a clear reason, limited duration, and audit awareness. If the goal is to let another employee do the work permanently, assign the correct permission set or transfer ownership instead.

Hands-on practice should include creating a limited test user in a Trailhead Playground or Developer Edition org. Assign a standard profile, then create a small permission set that grants access to a custom object or report capability. Log in as the user if allowed, or use permission inspection tools where available, and verify what changed. Then remove the permission set and verify the capability disappears. This teaches the difference between the baseline and the exception.

Onboarding workflow

Confirm the worker type, department, manager, region, and job tasks.

Choose the correct user license and any required permission set licenses.

Assign the baseline profile and role based on job family and visibility needs.

Add permission sets or permission set groups for additional duties.

Set locale, language, time zone, default currency if relevant, and email settings.

Validate login, app access, object access, record visibility, and critical reports.

Document the access pattern so the next similar user can be onboarded consistently.

The safest admin habit is to solve the smallest true problem. If the user cannot open an object tab, check app navigation, tab visibility, object permission, and license. If the user can open the object but cannot see records, inspect role, sharing rules, teams, territories, queues, or ownership. If the user can see the record but cannot edit a field, inspect field-level security, page layout, record type, validation rules, and automation. User management questions reward that diagnostic sequence.