Lesson 18 of 22 · All lessons

Section 7 · Security and Access · 7% of exam

7.2 Record Sharing and Data Visibility

3 min read Updated Nov 19, 2026

Exam objective

Use a structured approach to resolve access problems without weakening security unnecessarily.

https://help.salesforce.com/s/articleView?id=sf.security_overview.htm&language=en_US&type=5 https://trailhead.salesforce.com/content/learn/modules/cert-prep-salesforce-certified-associate/study-up-on-the-data-model

Core concepts

Good troubleshooting starts with a precise report of the issue: user, record, object, action, expected behavior, actual behavior, and when it began. Confirm the user’s identity and app context, then test the same action with a comparable user. This separates a general configuration problem from a user-specific assignment or a record-specific sharing issue. Use the layer sequence. First determine whether login or session controls prevent access. Then check whether the object is available in the current app and whether the user has object permission. Next inspect field-level security for missing or read-only fields. Finally inspect record ownership, org-wide defaults, role hierarchy, teams, sharing rules, and manual sharing. If the user can view but cannot edit, determine whether the missing capability is object-level edit permission or record-level edit access.

Scenario: A new analyst can view Accounts but cannot edit a single Account assigned to another team. Do not immediately grant broad edit permission to all Accounts. Verify that the analyst should edit that record, then determine whether a team, sharing rule, or controlled ownership change is appropriate. If the analyst cannot edit any Account, inspect object permissions. If only one field cannot be edited, inspect field access and any business rule that makes it read-only.

Keep a security boundary in place while fixing the issue. Do not export sensitive data to a spreadsheet as a workaround, share credentials, or ask an administrator to perform routine work under a privileged account. Use an approved process, document the business reason, grant the narrowest access that resolves the need, and review whether the permission should expire or be removed later.

Exam scenarios often include a tempting broad option. Prefer the feature that matches the scope and maintains least privilege. If the objective is to let a defined group see qualifying records, a targeted sharing mechanism is usually more appropriate than an organization-wide permission. If the problem is a hidden field, page layout changes may be insufficient. If the report is missing from a folder, data sharing may not be the problem at all.

“View All” and “Modify All” are powerful object-level permissions. Do not use them to bypass a record-sharing design unless the requirement explicitly calls for that breadth and the organization approves it.

State the failed layer before selecting the fix: authentication, object, field, record, app navigation, or analytics asset access.

Extra concept

Extra concept: Periodic access reviews compare assigned access with current job responsibilities. They help detect stale permission sets and role assignments after transfers or project completion.

Key takeaways

  • Good troubleshooting starts with a precise report of the issue: user, record, object, action, expected behavior, actual behavior, and when it began.
  • Use the layer sequence.
  • Scenario: A new analyst can view Accounts but cannot edit a single Account assigned to another team. Official references: https://help.salesforce.com/s/articleView?id=sf.security_overview.htm&language=en_US&type=5

Check your knowledge

Answer exam-style Security and Access questions with answers and explanations.

Practice Security and Access
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

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

Get Complete Access