Field-level security versus page layout visibility
Key Takeaway
Field-level security controls whether a user can read or edit a field everywhere in the app. Page layouts affect fields only on detail and edit pages, so to fully block a field for a user, set field-level security to None.
Salesforce has two separate tools that affect which fields a user sees on a record. Field-level security, also called field permissions, is a security control that decides whether a user can read or edit a field anywhere in the app. Page layouts organize detail and edit pages. Because a page layout affects fields only on those pages, page layouts are not a way to secure data.
Field-level security
Field-level security sets whether users can view or edit each field on an object. Because it works field by field, you can protect a sensitive field, such as a salary or a social security number, without hiding the whole object. Salesforce recommends managing field-level security with permission sets and permission set groups.
Field-level security has three access levels. Their labels depend on where you set them.
| Permission sets and enhanced profile user interface | Original profile interface and field-level security page |
|---|---|
| Read and Edit | Visible |
| Read | Visible and Read-Only |
| None | None (both boxes cleared) |
Field-level security applies in every part of the app, including these places:
- Detail and edit pages
- Related lists
- List views
- Reports
- Search results
- Email and mail merge templates
- Custom links
- Connect Offline
- Experience Cloud sites and portals
- Synchronized and imported data
- The Salesforce APIs