Filtering pages by permissions in the backend
Hello,
We're running an association website on Sitefinity 5.4 and have given access to a few chapter admins to maintain their own section on our site. We've set it up so that a chapter admin will only have permission to edit his chapter's page and child pages.
The problem is when the chapter admin logs into the backend, he can still see all of the site's pages, and has to drill down into his chapter's section to find the pages he's allowed to edit. Is there a way to set up a filter in the sidebar of the Pages section that will only show the pages a user has edit permissions for?
Hello Josh,
Currently this is not possible out of the box. By design Sitefinity would display all pages and only the ones for which the user has permissions would be accessible (not grayed out). Mind that it is intentionally done so that the user can get a better perspective on where and how the page he is responsible for is standing in the website. Additionally Pages are hierarchical type of content and hiding the parent pages (if the permitted page is a child one for the user) would bring it out of context for the user.
However we find your suggestion interesting and we might engage into implementing a sample in future for it.
Hi Pavel,
Thank you for your reply. I'm not too worried about losing the hierarchical context for these pages (the pages a chapter admin would have access to would all be under a common Chapters -> [Chapter Name] sort of structure), and since the other filters and the search behavior seems to reformat the grid into a flat list with an added "Under TopLevel -> SecondLevel" indicator, I don't think it should be too big of a problem.
Just to be clear, there's no way to implement this currently?
Thanks,
Josh
Hello Josh,
Yes, you are correct. There is currently no way to filter the pages by user permissions and in addition, manipulating the tree view the way one would expect for this type of filter would be quite difficult.
You could try to plug in some javascript to hide the grayed out pages. However if the user is only allowed to manipulate some child page, its parent should stay visible and I believe this will not suffice with the "drill down" inquiry.