Section 2 · Salesforce Fundamentals · 18% of exam
2.2 Control Object, Field, and Record Access
Exam objective
Apply Salesforce features that restrict or extend object, record, and field access, and choose an appropriate sharing solution for stated requirements.
Salesforce access is layered. Organization-wide defaults establish the baseline record access for each object. Role hierarchy can open access upward when configured for an object. Sharing rules, teams, territories, manual sharing, and other supported mechanisms can extend access beyond that baseline. Profiles and permission sets grant object permissions and field-level access; they do not by themselves provide access to a particular record. A user generally needs both permission to perform an action on an object and access to the record on which they perform it. Begin with least privilege. Determine who needs to read, create, edit, or delete each object, which fields are sensitive, and which records they should see. Set object permissions with profiles and permission sets, and use permission-set groups where they simplify job-based assignment. Use field-level security to restrict sensitive fields across interfaces and APIs. Page layouts can hide or arrange fields for usability, but they are not a security boundary. A hidden field on a layout can remain accessible through another interface if field-level security allows it.
For record access, set the most restrictive organization-wide default that still supports the business process, then open access only where required. Use role hierarchy when managers need subordinate records and the hierarchy reflects actual management. Criteria-based or owner-based sharing rules grant access to defined groups; they do not take access away. Teams support collaboration on particular records, while territories support account and sales coverage Salesforce Certified Platform App Builder | SU ·26 guide alignment 4 models. Manual sharing is a targeted exception and may be less maintainable at scale. Choose the narrowest mechanism that matches the requirement.
Consider ownership, object relationships, and license constraints. Master-detail relationships inherit access from the master; lookup relationships do not automatically behave as master-detail. Some objects have special sharing behavior. Sharing recalculation and high record volumes can affect operations. A secure design also includes permission review, deactivation and reassignment processes, and testing with representative user accounts rather than only an administrator.
Applied scenario: Suppose a regional support group can read all open cases in its region, but only the case owner and their manager can edit. First grant the support users the required Case object read permission and field access. Keep the record default private if appropriate. Then use a criteria-based sharing rule to grant read access to the regional group for qualifying cases. Use ownership and role hierarchy for the owner-manager edit relationship. Verify that the sharing rule grants only read access and does not expose fields removed by field-level security. Test with one user inside and one outside each group.
Design and risk review: Common mistakes include assuming that a role grants object permission, that a profile alone controls record visibility, or that hiding a field in a layout secures it. Also verify whether a permission set adds more access than the person’s baseline role requires. Avoid using broad public defaults to solve a narrow collaboration need. For every proposed share, ask whether it can grant access only, what group it targets, how membership changes, and whether the business requirement calls for read or edit access.
Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.
Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.
Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result. Salesforce Certified Platform App Builder | SU ·26 guide alignment 5
Key takeaways
- Apply Salesforce features that restrict or extend object, record, and field access, and choose an appropriate sharing solution for stated requirements
- Choose the platform feature that fits the requirement, data, access, and operating context.
- Test realistic users, exceptions, dependencies, and lifecycle effects before release.
- Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/data_security https://help.salesforce.com/s/articleView?id=sf.security_sharing.htm&type;=5
