Jump to content
Sign in to follow this  
Kiwi Chris

Page based permissions hierarchy

Recommended Posts

I'd really like Processwire to have a robust page based permissions system rather than just template based out of the box.
If the page tree is compared to a file system, it would be nice to be able to set owner (user), group (role) and public permissions on a page and have this propagate to sub-pages unless explicitly over-ridden.

With a large site, it's quite possible to have multiple sections that use the same templates, but where editing needs to be assigned to different people, for different parts of a site.

I've seen some proofs of concept that have never been updated or maintained, so I'm sure it can be done, but this is a bit of a show-stopper for me with an otherwise excellent CMS.

I might be able to have a go at something myself, but since this is security related, and I haven't had a go at module development before, it would be really handy to have something robust that just works.

Share this post


Link to post
Share on other sites
3 hours ago, kixe said:

@Kiwi Chris Welcome! Could this module be a solution for you?
AdminRestrictBranch last update 12.04.2017, stable

Thanks, I'll have another look at that module. Last time I tried, I didn't seem to be able to get it to work, but it looks as though it's been updated since.

If I'm reading the description correctly, it's not quite what I'm looking for although it's a step in the right direction.

Some editors might have responsibility for more than one branch of the tree, so restricting to just a single branch isn't ideal.
Rather than restricting a role to a specific branch, it would be more useful to assign a role(s) to a branch, so that a given role can have access to multiple branches if necessary.

Share this post


Link to post
Share on other sites
2 hours ago, Kiwi Chris said:

Thanks, I'll have another look at that module. Last time I tried, I didn't seem to be able to get it to work, but it looks as though it's been updated since.

If I'm reading the description correctly, it's not quite what I'm looking for although it's a step in the right direction.

Some editors might have responsibility for more than one branch of the tree, so restricting to just a single branch isn't ideal.
Rather than restricting a role to a specific branch, it would be more useful to assign a role(s) to a branch, so that a given role can have access to multiple branches if necessary.

If there are issues with a given module, you can always post your query/questions in the sub-forum for that module:

You can also report technical issues/possible bugs with modules directly at the particular  Project Page (Github) location:

https://github.com/adrianbj/AdminRestrictBranch

On the ProcessWIre Modules Page, for each module --- it lists the links to both the Forum Support and Project Page (Github):

http://modules.processwire.com/modules/admin-restrict-branch/

pw-help-links1.thumb.png.8ba682f831b6815bc77cc9a912832199.png

I would encourage everyone to use these essential resources to let the module authors know about bugs, possible changes or any other issues with their module.  Most module authors are willing to make changes to how things operate based on the comments or queries from module users.

  • Like 4

Share this post


Link to post
Share on other sites
13 hours ago, Kiwi Chris said:

I've seen some proofs of concept that have never been updated or maintained, so I'm sure it can be done, but this is a bit of a show-stopper for me with an otherwise excellent CMS.

I might be able to have a go at something myself, but since this is security related, and I haven't had a go at module development before, it would be really handy to have something robust that just works.

We've been using UserGroups for this use case for a few years now. This might be one of those unmaintained projects you were referring to, but if that's the case, it's mainly because it has been working just fine. No need to fix what isn't broken :)

That being said, we haven't been using UserGroups with ProcessWire 3.x, so can't really say for sure how well those two work together.

  • Like 3

Share this post


Link to post
Share on other sites
On 13/05/2017 at 4:42 AM, teppo said:

We've been using UserGroups for this use case for a few years now. This might be one of those unmaintained projects you were referring to, but if that's the case, it's mainly because it has been working just fine. No need to fix what isn't broken :)

That being said, we haven't been using UserGroups with ProcessWire 3.x, so can't really say for sure how well those two work together.

Thanks. That looks like it's exactly what I need. I'll test it to see how it works with Processwire 3.x, but hopefully it will work fine.
It doesn't seem to be in the official modules directory, so that might be why I missed it.
I can use the Site Profile Exporter module to set up my own site profile with the module included.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By DanielKit
      Hi. I'm currently stuck at the login page in my project. Once I enter my admin username and my password and press login, nothing happens. The page just reloads. However, the URL changes from http://myipaddress/processwire to http://myipaddress/processwire/?login=1. I've checked all of my server settings, and to my knowledge, all seems to be fine there. I don't know where to go from here.. Thanks in advance!
    • By VeiJari
      Hi, this is the first we are trying to make a page that has only one type of user that has access to every page. 
      The other users should only have a given access to specific pages, not to the whole template.
      My structure
      -Field -Organisation -Project -Report I want that the "measurer" role only has access to "project x" and it's children, but no view access to every project, organisation or field. I've tried to do this with https://modules.processwire.com/modules/page-edit-per-user/ but it still needs a view access to the whole tree to see the "project x" page. Or is there something I haven't figured out?
      Maybe I have to make it via the API: a select field in the "organisation" template where the admins could add the users and then I use hook to update the privileges?
      Have you done something like this and how did you accomplish it?
      Any help would be appreciated.
       
    • By modifiedcontent
      Small annoyance: I get a horizontal scrollbar in UIkit admin area - or actually Admin Theme Boss based on Uikit 3. I tried to fix it with CSS, but had trouble isolating/targeting it and don't want to mess with module or core files. I think this issue has been reported before. Is there a recommended fix? 
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • By codevark
      The Minimal Site works fine, but if I try to login as admin, I have no idea what the credentials are.
      I did not do the "install" process myself. The OVA came with everything set up, but there's no mention of the PW admin credentials being set to some initial value.
      Wondering if anyone else has tried the Bitnami OVA and if there's a simple answer.
      --Pete
×
×
  • Create New...