You are here:
Enable Field-Level Security for Permission Sets during Field Creation
Set field-level security for a field on permission sets instead of 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 instead of profiles.
| Available in: all editions |
| User Permissions Needed | |
|---|---|
| To enable setting field-level security for permission sets instead of profiles during field creation: | Customize Application |
To follow best practices for user access control, you plan to assign permissions through permission sets and permission set groups. For easier permission set management, turn on Field-Level Security for Permission Sets during Field Creation. When you create a field, you can then set field-level security on your permission sets as part of the workflow.
Now when you create a field on an object, set field-level security on a field, or change a field’s type, you assign field-level security for permission sets instead of profiles.

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.