Professional Documents
Culture Documents
Several factors control whether users can view and edit specific fields in Salesforce. You can control users’ access to fields at
the record type, user, or field level.
REQUIRED EDITIONS
Page layouts—Set whether fields are visible, required, editable, or read only for a particular record type.
Field-level security—Further 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.
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.
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions
For Knowledge validation status picklists, from Setup, enter Validation Statuses in the Quick Find box,
then select Validation Statuses.
NOTE In this user interface, you can’t check access for permission sets.
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions
In the Field-Level Security section of the page, specify the field's access level for the profile.
Field-Level Security
Field-level security settings let you restrict users’ access to view and edit specific fields.
REQUIRED EDITIONS
Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions
Page layouts and field-level security settings determine which fields a user sees. The most restrictive field access settings of the
two always applies. For example, you can have a field that’s required in a page layout but is read-only in the field-level security
settings. The field-level security overrides the page layout, so the field remains read-only.
Organize the fields on detail and edit pages by creating page layouts.
TIP Use field-level security to restrict users’ access to fields, and then use page layouts to organize detail and edit
pages within tabs. This approach reduces the number of page layouts for you to maintain.
NOTE Roll-up summary and formula fields are read-only on detail pages and not available on edit pages. They can also be
visible to users even though they reference fields that your users can’t see. Einstein Insights can also be visible to user even
though the insight references fields that your users can’t see. Universally required fields appear on edit pages regardless of field-
level security.
The relationship group wizard allows you to create and edit relationship groups regardless of field-level security.
Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions
1. From Setup, open Object Manager, and then in the Quick Find box, enter the name of the object containing the field.
2. Select the object, and then click Fields & Relationships.
3. Select the field you want to modify.
4. Click Set Field-Level Security.
5. Specify the field's access level.
6. Save your changes.