This is a regression from 1.12 and before that has been marked as a “Not a bug” as it was a deliberate decision:
I really feel very strongly that you should be able to set custom Bricks editor permissions for individual WP users, whatever user permissions they are.
For agency workflows many clients need Administrator privileges for various reasons but we don’t want these clients being able to destroy the layout of the site by fiddling with the builder. We also have a variety of experience levels in the team and we’d like to be able to roll out slightly reduced privileges to certain internal team members.
This was possible in some limited fashion in all previous versions of Bricks. It’s also possible with Oxygen builder.
Using custom permission plugins in WP is a pain and doesn’t work well with all plugins all the time and We don’t want to go back through 50 Bricks sites generating custom permission levels for clients.
Please consider changing this decision to lock all administrator accounts into having full access.
I completely agree with this request. The ability to set Bricks editor permissions per user, regardless of their WP role, is essential for agency workflows. We also have client sites where administrators need backend access but should not touch the builder. It was a very useful safeguard in 1.12 and earlier.
Relying on custom permission plugins is not practical at scale and introduces unnecessary risk. Please consider bringing this flexibility back to maintain the level of control and client safety that many of us depend on.
Although the original behavior (even before 2.0-alpha) was to always grant administrators the ‘Full access’ builder capability, there were some unintended workarounds. For example, if you removed the manage_options capability from an administrator, you could then modify their builder access, but this was not the intended approach.
Nevertheless, after further internal discussion, we now agree that it should be possible to adjust builder access on a per-user basis, regardless of their role. We have added this to our to-do list.