---
schema_version: "1"
id: 100b2321c835484b75b40dd716136fbaeaa0381ae62f50102d1ea4988ac97d59
title: Field Permissions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/users_profiles_field_perms.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.users_profiles_field_perms.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 007fc8da0f191a861ef4dc1982129aa79fd2feab51531c4de78b869517658793
description: Field permissions, or field-level security, lets you specify whether users can view or edit each field for an object.
products:
  - Security
  - Salesforce Platform
release: "264"
---
# Field Permissions

Field permissions, or field-level security, lets you specify whether users can view or edit each field for an object.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, <strong>Developer</strong>, and <strong>Database.com</strong> Editions</td></tr></tbody></table>

Your Salesforce org contains lots of data, but you probably don’t want every field accessible to everyone. For example, your payroll manager probably wants to keep salary fields accessible only to select employees. By setting field permissions, you can restrict user access in:

- Detail and edit pages
- Related lists
- List views
- Reports
- Connect Offline
- Email and mail merge templates
- Custom links
- Experience Cloud sites and portals
- Synchronized data
- Imported data
- Salesforce APIs

We recommend that you use permission sets and permission set groups to manage your users’ permissions. Because you can reuse smaller permission set building blocks, you can avoid creating dozens or even hundreds of profiles for each user and job function.

In permission sets and the enhanced profile user interface, the setting labels differ from those in the original profile user interface and in field-level security pages for customizing fields.

  
| Access Level | Enabled Settings in Permission Sets and Enhanced Profile User Interface | Enabled Settings in Original Profile and Field-Level Security Interfaces |
| --- | --- | --- |
| Users can read and edit the field. | Read and Edit | Visible |
| Users can read but not edit the field. | Read | Visible and Read-Only |
| Users can't read or edit the field. | None | None |

To further customize field access, you can

- Organize the fields on detail and edit pages by creating page layouts. Page layouts and field-level security settings together 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.
    
    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.
- Customize search layouts to set the fields that appear in search results, in lookup dialog search results, and in the key lists on tab home pages. To hide a field that's not protected by field-level security, omit it from the layout.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-access-264-0-0-production-enus/a92be132-3cbc-412a-9262-130636120c14/images/icon_note.png)

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 the 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.

- **[What Determines Field Access?](https://help.salesforce.com/s/articleView?id=platform.customize_fieldaccess.htm&release=264.0.0&type=5)**  
    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.
- **[Verify Access for a Particular Field](https://help.salesforce.com/s/articleView?id=platform.checking_field_accessibility_for_a_particular_field.htm&release=264.0.0&type=5)**  
    See whether access to a field is restricted and at what level—record type, user profile, or field.
- **[View the Field Access Summary in Object Manager](https://help.salesforce.com/s/articleView?id=platform.users_field_perms_summary.htm&release=264.0.0&type=5)**  
    See the permission sets, permission set groups, and profiles that grant access to a specific field, and the level of access granted.
- **[Modify Field Access Settings](https://help.salesforce.com/s/articleView?id=platform.modifying_field_access_settings.htm&release=264.0.0&type=5)**  
    From the field accessibility grid, you can change a field’s accessibility in the page layout or in field-level security.

#### See Also

- [Field Permissions](https://help.salesforce.com/s/articleView?id=platform.users_profiles_field_perms.htm&release=264.0.0&type=5 "Field permissions, or field-level security, lets you specify whether users can view or edit each field for an object.")
- [Object Permissions](https://help.salesforce.com/s/articleView?id=platform.users_profiles_object_perms.htm&release=264.0.0&type=5 "Object permissions specify the base-level access users have to create, read, edit, and delete records for each object.")