#OWD Access5 人がディスカッション中

Hi @Abhiram Sailada Good question! Even when OWD is Private, users can still access records through other sharing mechanisms.

In real-time projects, I usually check in this order:

1. Profile & Permission Sets: Check for View All, Modify All, View All Data, or Modify All Data permissions.
2. Role Hierarchy: Check whether the user is above the record owner in the hierarchy.
3. Sharing Rules: Check owner-based and criteria-based sharing rules.
4. Manual Sharing: Verify whether the record was shared directly with the user.
5. Account/Opportunity/Case Teams: Check whether team membership provides access.
6. Other Access: Check public groups, territories, and Apex-managed sharing where applicable.

Open the record's Sharing Hierarchy (if available) and use the User Record Access information to investigate the user's access.

Also, remember that OWD Private doesn't mean nobody else can access the record. It only defines the default level of record access.

The key is to identify which permission or sharing mechanism is granting additional access.

Hi @Yella Vani

As a Salesforce fresher, you don't need expert-level knowledge, but you should have a strong understanding of security concepts with practical examples. 

Focus on these key areas:

1. OWD: Understand Private, Public Read Only, and Public Read/Write with real-time scenarios.
2. Role Hierarchy: Know how record access can be provided to users higher in the hierarchy.
3. Sharing Rules: Understand Owner-Based and Criteria-Based Sharing Rules and when to use them.
4. Profiles: Understand baseline permissions, object access, field-level security, and login restrictions.
5. Permission Sets: Know how to provide additional permissions without changing the user's profile.
6. Practical Scenarios: Practice questions like:
   • Two users have the same profile but see different records. Why?
   • A user can view a record but cannot edit it. What could be the reason?
   • How do you provide record access to another department?

My suggestion: Don't just memorize definitions. Create 3–4 users in a Developer Org and test different security settings.

For fresher interviews, practical understanding and the ability to explain real-world scenarios are more important than advanced concepts.