#Salesforce Developer #OWD Access #Sharing Rules
In a real Salesforce project, how can we systematically troubleshoot record-access issues when a user can view or edit a record despite restrictive organization-wide defaults (OWD), and how do profiles, permission sets, role hierarchy, sharing rules, and teams affect access?
Hi @Sai Pavani Yamsani Good question! Salesforce Security is one of the most important topics for Admin and Developer interviews.
1. Core Security Concepts to Master
- OWD: Defines the default record access.
- Profiles & Permission Sets: Control object, field, and system permissions.
- Role Hierarchy: Allows users higher in the hierarchy to access records owned by users below them, based on sharing settings.
- Sharing Rules: Automatically provide additional record access.
- Manual Sharing: Share individual records with specific users or groups.
- Account & Opportunity Teams: Provide record access to team members.
- View All / Modify All: Allow users to bypass normal record-sharing restrictions.
2. How to Troubleshoot Record Access
If a user can access a record even when OWD is Private:
- Check the user's Profile and Permission Sets.
- Verify View All / Modify All permissions.
- Check record ownership and Role Hierarchy.
- Review Sharing Rules and Public Groups.
- Check Manual Sharing and Team access.
- Open the record → Sharing Hierarchy → View to identify why access was granted.
- For advanced debugging, check UserRecordAccess and the object's Share records.
3. Official Salesforce Documentation
Create two users with different roles, set Account OWD to Private, and test access using Sharing Rules, Permission Sets, and Role Hierarchy.
Interview Tip: Don't just explain what OWD or Sharing Rules mean. Be ready to explain how you identified and fixed a real record-access issue.
Hope this helps!
Venkat Yadav | SFDCINDIA
