You are here:
Set Field-Level Security for a Field on All Permission Sets
Set field-level security for a field on permission sets. This option is an alternative to setting field-level security for a field on profiles.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Set field-level security for a field on permission sets. This option is an alternative to setting field-level security for a field on profiles.
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| User Permissions Needed | |
|---|---|
| To set field-level security: | Manage Profiles and Permission Sets AND Customize Application |
In some cases, you want users to have access to an object, but you don’t want every field accessible to them. For example, you want certain account information accessible only to select employees. By configuring field permissions, or field-level security, you can control the specific fields that a user can see and edit on object records.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.