Business Use Case

Martin Jones is working as a System Administrator at Gurukul on Cloud (GoC). Martin is currently working on a field service implementation project.

He has a requirement to create a custom field Out of Business (Picklist, Yes/No) on the account object and set up the permission for the following permissions sets as mentioned in the table below.

Field-Level Security for Permission Set	Read Access	Edit Access
Field Service Admin Permissions	Yes	Yes
Field Service Agent Permissions	Yes	Yes
Field Service Community Dispatcher Permissions	Yes	No
Field Service Dispatcher Permissions	Yes	No
Field Service Integration	Yes	Yes
Field Service Resource Permissions	Yes	No
Field Service Self Service Permissions	Yes	No
View All Account	Yes	No

Automation Champion Approach (I-do):

One of the things I like about Salesforce is listening to its customers and enhancing products based on their feedback. Dynamic Forms, Dynamic Related List, and Custom Address fields are a few examples.

While reviewing winter’23 release notes, I stumbled across one feature: Set Field-Level Security for a Field on Permission Sets Instead of Profiles During Field Creation (Beta); I found it very helpful over many other features.

Let’s take a few minutes of pause here to understand the problem first.

These days, we’re implementing App security via Permission Set only and keep the number of profiles to the bare minimum. We also use permission sets to grant applications, objects, and field access.

The problem arises when we start creating new fields. In step 3, Salesforce allows you to assign field permission to the profiles.

But, in many scenarios, we want to use permission sets to assign field access – In such cases, you have to open every permission set and grant the field permission one by one. That is too much time investment.

What if, Salesforce allows you to set field permission for a Field on Permission Sets Instead of profile?

In this article, I will walk through the step-by-step instruction for setting field-level security for a field on permission sets instead of profiles during field creation.

Guided Practice (We-do):

After the winter’23 release, when you create a field on an object, you can follow best practices and set field-level security for a field on permission sets instead of profiles. And rather than manually granting access to a field in each permission set, you can set field-level security on permission sets during field creation. This feature is also available when you set field-level security on a field or change the field type on a field.

Enable Field-Level Security for Permission Sets During Field Creation (beta) in User Management Settings.
Create a Custom Field on the Account Object
1. Click Setup.
2. In the Object Manager, type Account.
3. Select Fields & Relationships, then click New.
4. Select Picklist as Data Type, then click Next.
5. Enter Field Label and click the tab key, the Field Name will populate.
  1. Enter the details:
    1. Values select Enter values, with each value separated by a new line
      1. Yes
      2. No
    2. As a best practice, always input a description and Help Text.
    3. Click on the Next button.
6. Set the Field-level Security on the permission sets.
7. Add this field to Page Layout.
8. Click Save.

Things to Remember

The list includes permission sets that have Create, Read, Edit, or Delete access on the field’s object. If no permission sets have that access on the field’s object, the list contains all the permission sets.
If you want to assign field-level security to profiles, then turn off Field-Level Security for Permission Sets During Field Creation (beta) in User Management Settings.

Formative Assessment:

I want to hear from you!

What is one thing you learned from this post? How do you envision applying this new knowledge in the real world? Feel free to share in the comments below.