Field-level security versus page layouts for protected health fields
Key Takeaway
To keep a protected field from a user everywhere in the app, use field-level security. Page layouts mainly organize detail and edit pages.
Some records hold sensitive data, such as protected health details, that only some users should see or change. Field-level security and page layouts both affect which fields a user sees. Only field-level security actually blocks access to a field everywhere in the app, while page layouts mainly arrange fields on detail and edit pages.
Field-level security versus page layouts
Field-level security protects a sensitive field without hiding the entire object, so a user can still work on the record while the protected field stays out of reach.
Field-level security and page layouts differ in what they set and where they apply.
| Field-level security | Page layouts | |
|---|---|---|
| What it sets | Whether a field is visible, editable, or read only | Whether fields are visible, required, editable, or read only for a particular record type |
| Where it controls field visibility | Every part of the app: object records, related lists, list views, reports, and search results | Detail and edit pages only |
You assign page layouts to users by profile and record type. Search layouts are different, because all users use the same search layouts.