This article is more of a reminder for me on how to do this than anything earth-shattering. In a recent project, I needed to change a field and limit access to only admins and editors (we have a custom role that is very restricted). I assumed in the conditional formatting that there would be the ability to choose a user role, but this is not the case. After spending an hour or so searching the web, I was about to give up, and then I stumbled across a code solution — not really what I wanted. After reviewing the code, it dawned on me that this might be a group versus a field-level setting. I was correct.

Meta Box Advanced Location Rules

In the field group setting is the section for the “Advanced location rules,” which provides a huge range of options. I had never really scrolled to the bottom of the list, but low and behold, user role and user are options.

Change the Field Without Losing Data

In this instance, I didn’t want to lose the data that was already loaded, so I noted the existing field name, removed it from the unrestricted field group, saved it, then created a field of the same type, added the field name, and set the restriction on the group. It works perfectly. Since I used the same name, the data remained, and the dynamic date in Bricks Builder was unaffected.

I hope that this option is added as a field-level value in the future, as this approach may not always be appropriate. If it is implemented, there will be challenges, especially related to layout.