Permissions to Standard Objects, Custom Objects, and Fields27% of the exam
Field-level security and View All Fields
How Read and Edit field permissions protect a field in every interface while page layouts only shape detail and edit pages, which fields field-level security can't fully control, when the View All Fields object permission fits, and how to manage and audit field permissions at scale.
Given a scenario, recommend the correct level of field permissions needed to provide the appropriate access to a set of users.
~8 min read · 16 practice questions ·
What the exam expects
- Choose Read and Edit, Read, or no access on a field so it holds in pages, list views, reports, sites and APIs, and say why a page layout alone doesn't.
- Predict the result when page layout and field-level security disagree, and use layouts for record-type differences.
- Spot fields field-level security can't fully control: formula, roll-up summary, universally required, master-detail, shared activity fields and lookup names.
- Recommend View All Fields when a persona needs every field on one object, and know what it doesn't change.
- Manage and audit field permissions at scale with permission sets, Set Field-Level Security and FieldPermissions queries.
Key terms: field-level security (field permissions: whether a user can view or edit a field); universally required field (required in the field definition); View All Fields (object permission revealing every field on one object); FieldPermissions (API object holding field permissions per permission set).
Key facts
Field-level security scope
- Detail
- Pages, related lists, list views, reports, imports, Experience Cloud sites, APIs
Layout versus field-level security
- Detail
- Most restrictive setting always applies
Permissions to set field-level security
- Detail
- Manage Profiles and Permission Sets and Customize Application
Formula field permissions
- Detail
- Only PermissionsRead can be inserted or updated
No FieldPermissions rows
- Detail
- OwnerId, master-detail and universally required custom fields
Clearing Read
- Detail
- A FieldPermissions record without PermissionsRead is deleted
Roll-up summary
- Detail
- Includes detail fields hidden by field-level security
View All Fields in the API
- Detail
- PermissionsViewAllFields from API version 63.0
View All Fields (Global)
- Detail
- Available only for the Platform Integration User
Field Accessibility page
- Detail
- Can't check access for permission sets
Sources for this section (7)
- Field Permissionshelp.salesforce.com (opens in a new tab)
- Set Field Permissions in Permission Sets and Profileshelp.salesforce.com (opens in a new tab)
- FieldPermissions (Object Reference)developer.salesforce.com (opens in a new tab)
- Roll-Up Summary Fieldhelp.salesforce.com (opens in a new tab)
- ObjectPermissions (Object Reference)developer.salesforce.com (opens in a new tab)
- View All and Modify All Permissions Overviewhelp.salesforce.com (opens in a new tab)
- Verify Access for a Particular Fieldhelp.salesforce.com (opens in a new tab)
- Why does a field that is required on the layout but Read in field-level security show as read-only?
- When would a FieldPermissions query return no rows for a field users clearly see?
- Which permission shows every field on one object without per-field settings while respecting sharing?
- Why can the Field Accessibility page show a field as hidden for users who can see it?
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 (16 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams