I like PageBuilder, but I don't want to let anybody touch it.
It is way too easy for well-meaning people to break things, and it's even easier for ill-meaning people to ruin things that ought not be ruined. The all-or-nothing approach that we have now means that all PageBuilder duties fall on the shoulders of a select few people in our newsroom.
(While we're at it, can we please get a prompt or something that asks users to "Use Shared" the second they open up a page, especially if it's been awhile? Stuff gets overwritten all the time simply out of carelessness.)
I think some sensible permissions could include:
Creating and deleting pages
Adding/editing certain content types
Publishing new changes
Making changes to linked features
On a deeper level, it would be great to have the ability to give a user access to only specific pages. For example, let's say Aaron is put in charge of managing the PageBuilder page for a special advertiser section. I would want him to be able to manage the content on that page but not be able to modify the homepage or any other section fronts.
Hi all – our PageBuilder Editor 3.23 release (scheduled to be released to Production on 9/30/25) has a long-awaited update: The Write and Publish privileges in PageBuilder now respect website settings configured in the Permissions application. This update should help multisite customers to grant more editorial users access to PageBuilder, since you can now restrict their access to only the pages assigned to their website(s).
Previously, if a user had Write or Publish privileges for any website, they were able to write or publish changes to all pages, regardless of what websites that page was assigned to. Now, users can write and publish pages assigned to only websites they have permissions for, as configured in Squads in the Permissions application. The behavior matches what you're used to with stories in Composer - see more details here.
This change only affects multisite customers using PageBuilder Editor. For more details, see PageBuilder permissions by website.
I will keep this Idea open since it contains other suggestions for PageBuilder permissions, which are still on our radar.
the ability to assign users to groups, and PB pages to those groups, would be a big help. An especially big help would be to give a user access to a single page and only edit one block in that page, for example.
This is a great feedback. We are definitely looking into more feedback on permissions for different users. This is on our Roadmap for next year.
Also of concern in PageBuilder is the ability for anyone with access to change the URL of a page - even if they do not have publish permissions in PageBuilder, they can still instantly change the URL of a page with no warning or confirmation, or notice to any other user