Ideas for Arc XP

PageBuilder needs lots of permission settings

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.

  • Britton Peele
  • Aug 21 2020
  • Future consideration
  • Attach files
  • Admin
    Kirti Kamtikar commented
    15 Sep, 2020 07:19pm

    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.

  • Mike Katona commented
    1 Sep, 2020 03:41pm

    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