Lesson 6 of 29 · All lessons
Salesforce Platform Administrator
0 of 29 complete
1ADM-201 Exam Overview
  1. 1.1ADM-201 Exam Overview
2Configuration and Setup15%
  1. 2.1Company settings, fiscal year, business hours, currency, and defaults
  2. 2.2Declarative user interface configuration
  3. 2.3User setup, licensing, and lifecycle
  4. 2.4Organization security and identity controls
  5. 2.5Sharing model, record access, and folders
  6. 2.6Profiles, permission sets, groups, and muting
3Object Manager and Lightning App Builder15%
  1. 3.1Objects, schema, and relationship architecture
  2. 3.2Fields, formulas, and field dependencies
  3. 3.3Page layouts, Lightning pages, record types, and actions
4Sales and Marketing Applications10%
  1. 4.1Leads, opportunities, sales processes, and Path
  2. 4.2Campaigns, campaign members, and lead assignment
  3. 4.3Sales productivity, scoring, forecasting, and territories
5Service and Support Applications10%
  1. 5.1Case management, queues, and case assignment
  2. 5.2Support processes, auto-response, escalation, and Einstein for Service
6Productivity and Collaboration10%
  1. 6.1Tasks, events, and activity management
  2. 6.2Chatter, groups, and internal or external collaboration
  3. 6.3Salesforce mobile app configuration and user experience
  4. 6.4AppExchange, packages, AgentExchange, and Flow awareness
7Data and Analytics Management17%
  1. 7.1Importing, updating, transferring, deleting, exporting, and backing up data
  2. 7.2Matching rules, duplicate rules, and validation rules
  3. 7.3Reports and report types
  4. 7.4Sharing, folders, and report visibility
  5. 7.5Dashboards, components, filters, subscriptions, refresh, and licensing
8Automation15%
  1. 8.1Selecting automation tools for a business scenario
  2. 8.2Flow capabilities, types, configuration, and order of execution
  3. 8.3Approval processes, criteria, approvers, and outcomes
9Agentforce8%
  1. 9.1Agentforce capabilities, use cases, security, and permissions
  2. 9.2Agent Builder, prompts, instructions, testing, and conversation preview

Section 2 · Configuration and Setup · 15% of exam

2.5 Sharing model, record access, and folders

2 min read Updated Nov 13, 2026

Exam objective

Given a request, apply the sharing model using org-wide defaults, roles, hierarchy, public groups, teams, sharing rules, and report or dashboard folders. Org-wide defaults establish the baseline record access for an object. If a user needs more access, role hierarchy, sharing rules, teams, or manual sharing may extend access depending on the object and configuration. Roles support hierarchical access; public groups let administrators target sets of users, roles, or other groups in sharing rules. Use a team when collaboration is tied to particular records and members need defined access. Use sharing rules when a repeatable group of users needs access to records based on ownership or criteria. Check whether the requirement is to expose records broadly or only selected records; broadening the baseline can affect much more data than intended.

Report and dashboard folders control who can access the analytics asset. Record sharing controls which records appear in the report results. A user may have access to a report folder but still see fewer records because of record-level visibility.

Additional concepts

Record access is layered

Start with the object’s org-wide default, then consider ownership, the role hierarchy, teams, sharing rules, and other supported sharing mechanisms. Roles organize hierarchical access; public groups provide reusable audiences for sharing. A team is typically tied to collaboration on a particular record, while a sharing rule extends access to a defined population.

Analytics access is separate

A report or dashboard folder determines whether the user can open or manage the asset. Record sharing determines which rows the user can see, and field permissions can affect data availability. If someone opens a report but sees fewer rows, changing folder access may not address the cause.

A sales manager needs visibility into a subordinate team’s opportunities. Review the role hierarchy and object’s sharing baseline first; if only a subset of records should be shared, use a narrower team or sharing rule where appropriate.

Access is cumulative. Verify effective access from the affected user’s perspective after adding a sharing mechanism.

Key takeaways

  • Org-wide defaults form a baseline; sharing mechanisms can extend access.
  • Roles, public groups, teams, and sharing rules have different targeting models.
  • Folder access and record visibility are separate checks.

Check your knowledge

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

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

Ready for the real exam?

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

Get Complete Access