Section 2 · Security and Access · 20% of exam
2.1 Sharing architecture: records, fields, and inherited access
Exam objective
Given a scenario, determine the implications to record and field data access, including sharing models, parent control, hierarchies, folders, and Territory Management.
Salesforce access is layered. Object permissions determine whether a user can read, create, edit, or delete a type of record. Field-level security controls visibility and editability of individual fields. Record-level sharing determines which individual records the user can access. A user needs the relevant object permission, field permission, and record access for a requested action to work. A page layout can hide a field from a page, but it is not a security boundary; field-level security is the control for protecting sensitive data across interfaces and reports.
Start by reading the requirement as a scope question. If a user must never see salary data, use field-level security. If the user may see salary on some but not all employee records, combine field permissions with an appropriate record-sharing model. If a user can open a record but cannot edit it, inspect object permission, record access level, and field edit access separately. Permission sets can add permissions; they do not normally subtract access granted elsewhere. Minimize broad permissions such as View All or Modify All because they can bypass record-sharing restrictions. Organization-wide defaults establish the baseline for records owned by users. Private is appropriate when users should see their own records and receive access through defined sharing routes. Public Read Only permits viewing across the object while limiting edits to owners or authorized users. Public Read/Write broadens both viewing and editing. A setting of Controlled by Parent means access to a child is derived from its master record, a behavior tied to master-detail relationships. Sharing rules expand access to groups of users; they do not make the baseline more restrictive. Role hierarchy can grant access upward for supported objects when Grant Access Using Hierarchies applies. Additional access can come from ownership, role hierarchy, teams, manual sharing, criteria-based or owner-based sharing rules, territories, and implicit sharing. These mechanisms have different eligibility and maintenance characteristics. Territory Management supports account and sales assignment models that do not map neatly to the role hierarchy. When the scenario says a manager needs records from a particular territory, identify whether territory assignment and territory-based access meet the need before changing the organization-wide default. For standard objects, some access is implicit through relationships such as accounts and related contacts or opportunities; inspect the object's documented behavior.
Folder permissions are a separate layer. A user may have report or dashboard folder access but still lack access to the underlying records, or may have data access but be unable to open a report stored in a private folder. A dashboard running as a specified user can display data that viewers themselves could not otherwise access, subject to dashboard configuration and Salesforce rules. Treat this as a disclosure risk: choose the running user intentionally and restrict folder access. Email folders and other collaboration assets also have their own access controls; do not infer them from record sharing.
Scenario approach: determine the user persona, object, record population, required action, and any sensitive fields. Then map each requirement to the least broad layer that can satisfy it. Test with a representative user, not only as a system administrator. Use a record owned by another user and a field that should remain hidden. Confirm access through the user interface or access diagnostics and inspect reports and dashboards. If access is too broad, check additive grants such as role hierarchy, sharing rules, teams, territories, and View All before making the baseline more restrictive. Exam focus: distinguish field access from record access, and recognize that page layouts do not secure fields. Compare a baseline sharing change with an additive sharing rule. In a scenario involving inherited access, identify Controlled by Parent and master-detail behavior. For dashboards, check both folder access and the running-user context. For territories, reason about assignment and supported access rather than assuming the role hierarchy is the only mechanism. A correct answer typically satisfies the business need while keeping the broadest possible audience small.
Broad object permissions can make a carefully designed record-sharing model ineffective. Before granting View All, Modify All, or an administrator-like profile, test the actual access path and confirm that it is needed. Practical scenario
A sales operations analyst needs to report on all open opportunities in an assigned territory but must not edit them or see a restricted margin field. Keep the margin field hidden with field-level security, grant read access through the territory model, and ensure the analyst has Read on Opportunity. Store the report in a folder the analyst can access and review its dashboard running user. This meets the reporting need without changing the org-wide default to Public Read/Write. Extra concept
Implicit sharing is an extra access path administrators should remember when troubleshooting. It can provide access through parent-child and collaboration relationships, so a user's effective access may exceed what a simple review of ownership and sharing rules suggests. Use Salesforce's sharing details and access checks to identify the source rather than removing an unrelated permission.
Key takeaways
- Object, field, and record access solve different security questions.
- Use sharing rules and territories to expand access from a least-privilege baseline.
- Check report-folder access and dashboard running-user context separately.
- Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.users_profiles.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.account_contact_relationships.htm&type=5
