Page-layout required versus field-level security
Key Takeaway
When a page layout and field-level security disagree, the more restrictive setting wins.
Two settings decide what a user can do with a field. Field-level security, also called field permissions, controls whether a user can view or edit a field anywhere in the app. The main job of a page layout is to organize detail and edit pages by arranging the fields on them.
What field-level security controls
You set field-level security for each field on an object. The setting applies across the whole app, including these places:
- Detail and edit pages
- Related lists
- List views
- Reports
- Search results
- Email and mail merge templates
- Experience Cloud sites and portals
- Imported data
- Salesforce APIs
Field-level security has three access levels, and the labels depend on where you set them. Each row in this table shows one level under its two labels.
| In permission sets and the enhanced profile user interface | In the original profile user interface and on field-level security pages |
|---|---|
| Read and Edit | Visible |
| Read | Visible and Read-Only |
| None | None |