Hello,
Is there a way to restrict who can save over pages on a page by page basis?
We are having a lot of accidents with users who set certain filters or fields for themselves on shared pages and then saving them.
These same users do need to have permission to edit some project pages, but I can’t find a way to control pages permissions, it seems hard-coded by permission group, and while I can control what groups can view a page, I can’t find an equivalent way to set the save permissions.
Any hints?
Thanks
I don’t think this can be done at the minute. The only permission group differences I know of for page editing is that the default landing page for a specific entity type (i.e. the page you get sent to when you click on “Assets” or “CustomEntityXX”) requires a higher permission level than others. So as a workaround, if you have important pages you’d like to elevate, you might be able to make use of that.
This is definitely a feature we would absolutely love to make use of as well, though, if it were implemented. Another issue we have around collaborative page editing is how easy it is to accidentally override other users’ changes, especially since it counts updates to one tab to be an update to the page as a whole, so one user can’t save changes to one tab while another user saves changes to another tab.
Thanks for the reply.
Yeah we have an artist home page that’s used by a few hundred users and they’re always saving their own filters in there, it’s a constant battle.
Contact support, maybe they can make a conditional permission based on a field or something so that artists can only edit certain pages.
You could also encourage those users to make personal filters instead of global filters? Or instill the routine of reverting a page before making a change and saving it.
I’ve found that if there are a lot of cases of pages starting to be overwritten by different users then it’s a sign to start to restrict down the permission groups a bit and provide a little training.
Project pages would be restricted to producers being the only ones to edit/save. All users with project access can still save new pages or personal filters.
Global pages are restricted down to only the owner of a page can edit/save. Again everyone can save-as.
This is slightly annoying to maintain since people tend to make a lot of duplicates but it’s better then people saving over pages/filters that might be important to getting the work done.
It might also point to a need to customize the default pages more so they work for more users
Well, this is our artist home page, it’s assigned to 400+ users as their home-page, this is a global page but somehow everyone can save it, so I’m not sure how to restrict it.
If you uncheck this setting in the permission group that your artists are in, they will no longer be able to edit any global pages they haven’t created. They can always copy/save-as a page but not change some one else’s, ie your studio artist page.
Good to know, thanks. Turned off for artists, but we have other groups that have some global pages they need to be able to edit, so I can’t turn it off for them, would still be nice on a per page-level to be able to set who can edit, just like we can set who can view.
@PeteHart On your screenshot above (and in my permissions page) I can see “Edit Built-in home page”, do you happen to know which page this refers to? Maybe this is the page I should be modifying and setting as the artist home page since it looks like that page has a special status for permissions.
The “built-in home page” is a bit of a legacy thing. When a site is a create there is a default Home page. That permission will allow users to edit it. But since the option was added for all users to set their own home page it isn’t used much. At least from what I’ve seen. It’s still a useful tool for helping people grasp the concept but usually isn’t used for long.
You can find it under all pages:
Looks like this:
And yeah, fully understand if that global permission change doesn’t fully solve the issue. I try to encourage global shared pages to be owned by the heads of the respective groups. Then anyone put into the permission groups that allow for global page editing needs to be made aware what they can do. Now that we have page setting histories, it’s a lot less of an issue.
I do agree, a simple edit permission list right below the “private/shared” toggle would be very help but also be a huge headache when you combine that with existing page editing permissions.
I think this may be able to be done with conditional permissions, you can ask Sg Support if thats possible.
I’ll run like this for a bit and see how it goes, the history does help checking who’s making changes.
I found our default home page and it’s been modified to death by an early admin from years ago, who apparently thought it was not a shared page, seeing as they put their name in it everywhere.
1 Like
