Object permissions, View All and Modify All levels
How Read, Create, Edit, Delete, View All Records and Modify All Records stack and depend on each other, how they differ from View All Data and Modify All Data, and how a minimal profile, permission sets, permission set groups, muting and user access policies deliver the least-privilege level.
Given a scenario, recommend the right level of object permissions needed to provide the appropriate access to a set of users.
~8 min read · 20 practice questions ·
What the exam expects
- Pick the smallest set of object permissions (Read, Create, Edit, Delete, View All Records, Modify All Records) for a persona, including each level's dependencies.
- Choose between object-scoped View All / Modify All Records and org-wide View All / Modify All Data, knowing none grants field access or suits external users.
- Recommend a minimal profile plus permission sets and groups, with muting when one group must lose a permission.
- Name the system permissions that run a security model, and apply least privilege, defense in depth and fail securely.
Key terms: object permission (base-level access to one object); View All / Modify All Records (one object, overrides sharing); View All / Modify All Data (every object, overrides sharing); muting permission set (removes permissions inside one group); user access policy (automates access assignments).
Key facts
- Detail
- Requires Read and Edit on the same object
- Detail
- Requires Read, Delete, Edit and View All Records; Create isn't required
- Detail
- Child View All or Modify All Records needs parent View All Records; Setup fixes it on first save, the API doesn't
- Detail
- No View All or Modify All Records for ideas, price books, article types, products
- Detail
- Can't be assigned View All Data, Modify All Data, or View All, Modify All Records or View All Fields
- Detail
- ObjectPermissions returns Ids starting with "000" that can't be updated or deleted
- Detail
- Up to one muting permission set per permission set group
- Detail
- Lowest Order value wins when several active policies match
Sources for this section (5)
- Why can't Modify All Records be granted to a persona that must never delete records?
- When does a Setup save change permissions on a parent object you didn't touch?
- Which permission lets HR find every user when the User default is Private, without exposing other data?
- Why does muting Delete in a permission set group not stop a rep who still deletes records?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Sharing and Visibility Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 21 lessons of the Platform Sharing and Visibility Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (20 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams