Page Layouts and Field-Level Security | Salesforce
Page Layouts and Field-Level Security
Use field-level security to control user access to fields. Use page layouts to control the layout and organization of detail and edit pages in Salesforce, the Self-Service Portal, and the Salesforce
Customer Portal. Customize search layouts to change which fields display in search results and the buttons that display on list views.
Available in: both Salesforce Classic and Lightning Experience
Page layouts and search layouts available in: All Editions
Field-level security available in: Enterprise, Performance, Unlimited, Developer, and Database.com Editions
When you use page layouts to hide fields from detail and edit pages, users can still access them. Users see fields via reports, search results, list views, and the API. To restrict field access, use field-level security. Field-level security doesn’t prevent searching on the values in a field. When search terms match on field values protected by field-level security, the associated records are returned in the search results without the protected fields and their values. Also don’t use page layouts to secure data. For example, removing the Edit button from a page layout doesn’t prevent users from using inline editing. To prevent users from editing data, use sharing rules, field-level security, page layout field properties, validation rules, object permissions, and Visualforce pages.
Restrict users’ access to view and edit fields. For example, restrict access in reports, search results, list views, related lists, email and mail merge templates, custom links, Connect Offline. Also restrict API access and when synchronizing data or importing personal data.
Override less-restrictive field access settings in page layouts and mini page layouts. For example, if a page layout requires a field that’s read-only in field-level security settings, the field remains read-only for the user.
Override less-restrictive field settings in search layouts. For example, if a field is visible in the search layout but hidden via field-level security settings, the field remains hidden.
Control the layout and organization of detail and edit pages.
Control which fields, related lists, and custom links users see, on detail and edit pages only.
Control which standard and custom buttons display on detail pages and related lists.
Determine whether fields are visible, read only, or required, on detail and edit pages only.
Determine the fields that users can import data into.
In Personal, Contact Manager, Group, and Professional Editions, control which fields users can access in related lists, list views, reports, Connect Offline, email and mail merge templates, custom links, and when synchronizing data.
In Professional, Enterprise, Unlimited, Performance, and Developer Editions, determine aspects of mini page layouts, including:
fields and field access settings.
The visible fields and related lists of the mini page layout can be further customized. However, other items inherited from the associated page layout cannot be changed on the mini page layout. Mini page layouts display selected fields and related lists of records in the mini view of the console.
To automatically add a field to all page layouts and make it visible and required everywhere regardless of field-level security, make it a universally required field.