Hierarchical Priviledges

[artoo80]

Thank you for you work on the framework.

I appreciate your work on the framework. I really do.  I notice that currently  it is possible to add new privilege levels, so for instance (following the default implementation with user-admin level) we may have:

• Cleric
  
• Administrator
  
• Candidate
  
• Fresher
  
• Graduate
  
• Lecturer
  

However it does not seem to be possible to have (E.g.) "../users/account.php" page as a private page available to multiple user levels and it seems I can only add one user level at the time.

One option would be to consider that all these user levels are actually sub-level of "user" and create another table to allow the definitions of these. However, this seems a hack around your neat implementation and management of privileges using the Admin interface.

If I wanted one page (e.g.) "../usersc/lecture.php" to be private and available only to freshers, graduate and lecturer but not to candidates how do I achieve that without modifying the logic of your priviledge check?

I was trying to reverse engineer your permission check but then I thought I ask as maybe I have picked up the wrong end of the stick with this problem.

---

Thank you for you work on the framework.

I appreciate your work on the framework. I really do.  I notice that currently  it is possible to add new privilege levels, so for instance (following the default implementation with user-admin level) we may have:

• Cleric
  
• Administrator
  
• Candidate
  
• Fresher
  
• Graduate
  
• Lecturer
  

However it does not seem to be possible to have (E.g.) "../users/account.php" page as a private page available to multiple user levels and it seems I can only add one user level at the time.

One option would be to consider that all these user levels are actually sub-level of "user" and create another table to allow  the definitions of these.  However, this seems a hack around your neat implementation and management of privileges using the Admin interface.  

If I wanted one page (e.g.) "../usersc/lecture.php" to be private and available only to freshers, graduate and lecturer but not to candidates how do I achieve that without modifying the logic of your priviledge check?

I was trying to reverse engineer your permission check but then I thought I ask as maybe I have picked up the wrong end of the stick with this problem.

Like I said " I got the wrong end of the stick". You can set multiple privileges to users instead of doing so for pages. It makes sense.

Then I guess it will be easy to figure out how to set up features in the page that maybe drawn only in case a user has a specific priviledge.