Permissions to Standard Objects, Custom Objects, and Fields27% of the exam
UI visibility: layouts, Dynamic Forms and tab settings
Which user interface control hides a field, section, action, page or tab for whom (page layouts, record types, compact and search layouts, list views, Dynamic Forms, Dynamic Actions, Lightning page activation and tab settings), and why none of them is security.
Given a scenario, recommend the appropriate mechanism to hide data at the user interface level.
~7 min read · 16 practice questions ·
What the exam expects
- Separate a "declutter the screen" requirement from a "block the data" requirement, and reject UI controls as security.
- Pick the right UI control: page layout or record type, compact layout, search layout, list view sharing, Dynamic Forms visibility rule, Dynamic Actions filter, Lightning page activation or tab setting.
- Predict edge behaviour: hidden required fields, filters on fields the user can't read, per-page Dynamic Actions, Classic apps and Home pages, conflicting tab settings.
Key terms: page layout (fields, buttons and related lists on detail and edit pages per record type and profile); Dynamic Forms (fields and sections as Lightning page components with visibility rules); Dynamic Actions (actions assigned and filtered in Lightning App Builder); tab settings (Default On, Default Off, Tab Hidden).
Key facts
Field-level security reach
- Detail
- Records, related lists, list views, reports, search results
Case Close layouts
- Detail
- Same record type can use a different layout for closed cases
Compact layout assignment
- Detail
- One per record type; first fields show in header and lookup hover
Search layout and keyword search
- Detail
- Doesn't control which fields are searched
Manage Public List Views
- Detail
- Sees all public list views regardless of sharing
Hidden required field
- Detail
- Field Required in Lightning App Builder but hidden at run time can be saved empty
Visibility filter span
- Detail
- Record field values can't span more than five fields
Dynamic Actions scope
- Detail
- Applies only to the record page being edited
Conflicting tab settings
- Detail
- Most permissive setting applies
Sources for this section (8)
- What Determines Field Access?help.salesforce.com (opens in a new tab)
- Assign Record Types and Page Layouts in Profileshelp.salesforce.com (opens in a new tab)
- Compact Layoutshelp.salesforce.com (opens in a new tab)
- Search Layouts Limitationshelp.salesforce.com (opens in a new tab)
- Create a Custom List View in Lightning Experiencehelp.salesforce.com (opens in a new tab)
- Visibility Rules on Lightning Pageshelp.salesforce.com (opens in a new tab)
- Create Dynamic Actions in Lightning App Builderhelp.salesforce.com (opens in a new tab)
- Tab Settingshelp.salesforce.com (opens in a new tab)
- Why does a Dynamic Actions filter on a field the user can't read show the action anyway?
- When can a Home page component filter on a record field?
- Which control offers some users a picklist without one value?
- Why does Tab Hidden on a profile fail for users who also hold a permission set with Available on that tab?
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