What Determines Field Access?

• Field-level security (field permissions)—Restrict users’ access to fields by setting whether those fields are visible, editable, or read only. These settings override field properties set in the page layout if the field-level security setting is more restrictive. Field-level security controls the visibility of fields in any part of the app, including object records, related lists, list views, reports, and search results.
• Page layouts—Set whether fields are visible, required, editable, or read only for a particular record type.
• Permissions—Some user permissions override both page layouts and field-level security settings. For example, users with the “Edit Read Only Fields” permission can always edit read-only fields regardless of any other settings.
• Universally required fields—Override field-level security or any less-restrictive settings on page layouts by making a custom field universally required.
• Lookup and system fields—If you enable the Require permission to view record names in lookup fields setting, you restrict who can view record names in lookup and system fields. Users must have Read access to these records or the View All Lookup Record Names permission to view this data.

After setting these items, confirm users’ access to specific fields using the field accessibility grid.