Study guide
3.2 Profiles, Permission Sets, Permission Set Groups, and Muting
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
3.2 Profiles, Permission Sets, Permission Set Groups, and Muting
Key Takeaways Explain This Topic AI
Profiles provide the required baseline for users, while permission sets and permission set groups are the preferred way to add access by job function.
Permission sets are additive; they do not remove access already granted by a profile, another permission set, or a permission set group.
Muting permission sets reduce selected permissions inside a permission set group, but they do not mute permissions granted outside that group.
Troubleshooting permission problems requires separating app access, object CRUD, field access, record access, system permissions, license limits, and login restrictions.
Last updated: May 2026
Permission Sources Work Together
A profile is required for every Salesforce user and supplies baseline settings such as user license alignment, login hours, login IP ranges, object permissions, field permissions, app access, tab settings, record type assignments, page layout assignments, and some system permissions. Historically, many orgs placed most access in profiles. Current administration practice is to keep profiles lean and use permission sets and permission set groups to add job-specific capabilities.
Permission sets grant additional permissions to individual users. Permission set groups bundle multiple permission sets into a package that matches a role such as Sales Operations Analyst or Service Escalation Lead. This is easier to audit than assigning ten unrelated permission sets to each user one by one. It also helps with onboarding and mover workflows.
Source What it can do What to watch
Profile Required baseline; login controls; app, tab, object, field, record type, and layout settings. Too much access in profiles creates profile sprawl.
Permission set Adds object, field, app, system, and other permissions to selected users. It is additive and does not remove permissions.
Permission set group Bundles permission sets for easier assignment. Permission conflicts need clear design and testing.
Muting permission set Mutes selected permissions inside one permission set group. It does not mute access granted by the profile or another assignment.
User license Defines which features and permission sets are eligible. A user cannot receive incompatible access just because an admin wants it.
Object, Field, App, And System Permissions
Object permissions answer whether a user can create, read, edit, delete, view all, or modify all records for that object, subject to record access. Field permissions answer whether the user can see or edit specific fields. App and tab settings affect navigation. System permissions grant administrative capabilities such as running reports, exporting reports, managing users, customizing application areas, or using setup features.
A user who says they cannot find Accounts may have no tab visibility or app access. A user who can open Accounts but not create one may lack object Create permission. A user who can edit an account but not a sensitive field may lack field edit access. A user who can edit the field but gets an error after saving may be blocked by validation, automation, duplicate rules, or approval locks.
This separation is important because the least disruptive fix depends on the failed layer. Giving Modify All Data because a tab is hidden is a serious overgrant. Adding a tab to an app does not solve missing object Read. Editing a page layout does not solve field-level security.
Permission Sets Are Additive
Permission sets add access. If a profile grants Account Delete, assigning a second permission set without Delete does not remove the profile's Delete access. If one permission set grants Report Export and another does not, the user still has Report Export. This additive model is why access reviews must inspect the whole permission footprint.
Permission set groups are additive packages too. Muting exists because a group may include a broad permission set that should be partially restricted for a specific packaged job role. For example, a group might include Service Case Tools but mute Delete on Case for frontline users. The key exam trap is scope: a muted permission is muted only within that permission set group. If the user's profile or another permission set grants the same permission, the user still has it.
Use Setup > Users > Permission Set Assignments on the user record for a quick view. Use Setup > Permission Sets and Setup > Permission Set Groups for design and audit. Use Setup > Profiles for baseline settings and layout assignments. In a Trailhead Playground, practice assigning a permission set to a test user and checking the effective symptom by logging in as that user where policy allows.
Access Design Workflow
Use this design sequence for a new business role:
Identify the user license and feature license requirements.
Start from the standard or custom minimal profile used by that population.
List required objects, fields, apps, tabs, record types, and system permissions.
Group reusable job capabilities into permission sets.
Bundle the job role into a permission set group when several sets travel together.
Use muting only to remove selected permissions from that group's bundle.
Test with a non-admin user who has no extra legacy permissions.
Document why any broad permissions such as View All Data, Modify All Data, View All, or Modify All are required.
Scenario: Sales reps need to create and edit Opportunities, read Accounts, use the Sales app, and view a discount field only after promotion to senior rep. The baseline profile can cover login and common navigation, the sales permission set can cover Opportunity work, and a senior rep permission set can add field visibility. Do not clone a profile for every seniority level unless the org already has a governed profile model.
Troubleshooting Sequence
When a user cannot complete an action, write the sentence in this format: user, action, object, field, record, interface. For example, Morgan cannot edit Discount Approval Status on Opportunity O-100 from the Lightning record page. Then check layers in order.
License and feature access: is the user eligible for the object or feature?
Login and session controls: can the user get into Salesforce from the current network and time?
App and tab access: can the user navigate to the feature?
Object permission: does the user have the required CRUD permission?
Field permission: can the user read or edit the target field?
Record access: does sharing allow the requested record operation?
Record type and page layout: is the correct UI and picklist experience assigned?
Business logic: are validation rules, flows, approval locks, duplicate rules, or required fields blocking save?
This order prevents overcorrection. If the field is absent because field-level security hides it, changing the page layout is not enough. If the field is visible but read-only because the page layout marks it read-only, field-level security may not be the blocker. If the user sees the field and edits it but save fails, the answer may be automation or validation rather than permissions.
Exam Traps
Do not say permission sets reduce access. They add. Do not say muting removes profile permissions. It does not. Do not say a role grants object Create. Roles affect record access. Do not say a public group grants a system permission. Public groups help sharing and collaboration, but object and system permissions come from profiles, permission sets, and permission set groups.
Also watch license clues. A permission set cannot grant access to a feature the user's license does not support. If a scenario says the assignment fails, check license compatibility before redesigning the sharing model.