Study guide

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams

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.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams

Key Takeaways Explain This Topic AI

Org-wide defaults set the private baseline for record access; roles, sharing rules, teams, territories, and manual shares open access from there.

The role hierarchy normally grants record visibility upward to managers, but it is not the same thing as a company org chart or a profile.

Sharing rules are best for repeatable group access patterns, while teams and manual sharing are better for record-specific collaboration.

Record access troubleshooting starts with object permission, then the record's baseline sharing model, then ownership and sharing paths.

Last updated: October 2026

Start With The Record Access Baseline

Org-wide defaults, often shortened to OWD, answer the first record access question: what can a user do with records they do not own and that have not been shared to them another way? In Setup, use Sharing Settings to review object-level defaults such as Private, Public Read Only, Public Read/Write, Controlled by Parent, and external sharing defaults where available. OWD does not grant object CRUD. A user still needs object permission from a profile or permission set before record sharing can matter.

Think of record access as a gate sequence. First, can the user log in and use the app? Second, does the user have object permission such as Read, Create, Edit, or Delete? Third, does the user have record access through ownership, OWD, role hierarchy, sharing rule, team, territory, queue, manual share, implicit parent-child access, or a broad permission such as View All or Modify All on the object? If any required gate fails, the user sees a symptom.

Tool Best use Common trap

OWD Set the default record privacy baseline for each object. Treating OWD as the final answer when access can still be opened.

Role hierarchy Let managers above owners see subordinate records. Designing it as a perfect HR chart instead of a data visibility hierarchy.

Sharing rule Open access for predictable groups of users. Using one-off rules for exceptions that are really team or manual shares.

Account team Share a specific account with named collaborators. Forgetting related opportunity or case access settings.

Opportunity team Share and define sales collaboration on one opportunity. Assuming it changes account ownership.

Case team Share a support case with collaborators. Assuming it applies to every future case automatically.

OWD Choice And Scenario Judgment

Private is appropriate when users should see only their own records unless another sharing mechanism opens access. Sales opportunities, sensitive cases, custom application records, and compensation-related objects often start private. Public Read Only works when broad visibility is allowed but uncontrolled editing is not. Public Read/Write is a broad model and should be chosen only when business policy accepts open record editing for that object.

Controlled by Parent means access to a child record follows access to the parent. It is common in master-detail relationships and some standard relationship behaviors. If a custom child object is Controlled by Parent under Account, asking who can see the child starts with who can see the parent account. Exam scenarios often hide this clue in the data model description.

External defaults matter when Experience Cloud, partners, or external users are involved. External users frequently need a stricter baseline than internal users. If a scenario separates internal sales employees from partner users, do not assume the same OWD applies to both audiences.

Role Hierarchy Opens Upward

The role hierarchy grants access upward from record owners to users above them in the hierarchy when the object allows hierarchy-based access. A sales rep who owns an opportunity may be visible to the regional manager above that rep, even if Opportunity OWD is Private. The role hierarchy is about data visibility, not login ability, field access, or app navigation.

Do not confuse roles with profiles. A profile or permission set grants what the user can do to an object. A role helps decide which records the user can access. A user can have the System Administrator profile and no role, or a highly placed role and a restricted custom profile. The effective result depends on both tracks.

A good role design supports reporting and management visibility. It does not need to mirror every dotted-line reporting relationship. Too many roles create maintenance overhead and can slow sharing recalculations. Too few roles force excessive sharing rules. The administrator's job is to model the record visibility policy with enough precision and stability.

Sharing Rules, Teams, And Manual Shares

Sharing rules open record access for many records that meet defined criteria or ownership patterns. Owner-based rules share records owned by one role, role-and-subordinates group, queue, or public group with another group. Criteria-based rules share records when fields match defined values. For example, high-priority cases in a region can be shared with an escalation queue or support manager group.

Teams are record-specific collaboration tools. Account teams, opportunity teams, and case teams are useful when a named group of people works one record or customer relationship. They are more flexible than a global sharing rule when collaboration varies record by record. Manual sharing is even more direct, but it is best for exceptions, not primary architecture.

Public groups package users, roles, roles and subordinates, territories, or other groups for sharing. They are reusable and help avoid hard-coding access one user at a time. When a sharing rule says share with Sales Operations, the clean implementation is usually a public group maintained by policy, not dozens of individual shares.

Access Decision Workflow

Use this workflow when selecting a sharing mechanism:

Confirm the user needs access to records, not merely a tab, app, or field.

Confirm object permission exists for the needed action.

Set OWD to the most restrictive baseline that matches business policy.

Use the role hierarchy for manager visibility that follows ownership structure.

Use sharing rules for repeatable groups or criteria.

Use teams for record-specific collaboration on accounts, opportunities, and cases.

Use manual sharing only for approved exceptions.

Use View All or Modify All on the object only when broad administrative access is intended.

Scenario: Opportunity OWD is Private. Sales reps should see only their own opportunities, regional managers should see their reps' opportunities, and a Deal Desk group should see all opportunities over a threshold. The baseline is Private, the manager path is the role hierarchy, and the threshold access is a criteria-based sharing rule to a public group. Public Read/Write would be too broad.

Scenario: One strategic account needs an implementation specialist added for six months. An account team is cleaner than a new org-wide sharing rule. If every strategic account needs implementation visibility, then a criteria-based sharing rule or territory design may be better.

Troubleshooting Sequence

When a user cannot see a record, do not start by changing OWD. First identify the exact user, object, record, action, and expected result. Check object Read permission. Check whether the user owns the record. Check the OWD. Check role hierarchy position. Check public group membership, sharing rules, teams, territories, queues, manual shares, and broad object permissions. Then test with a controlled user or Login-As workflow if policy allows.

When a user can see but cannot edit, the issue may be record access level, object Edit permission, field-level security, record type, validation rule, approval lock, page layout, flow, or ownership. Record visibility and editability are not the same. This distinction is a frequent exam trap because the symptom says access but the fix may be object permission or field access.