search

apeisa / UserGroups

Adds users groups and page based permission to ProcessWire
GNU General Public License v2.0
11 stars 4 forks source link

Default access definitions #21

Closed niklaka closed 10 years ago

niklaka commented 10 years ago

cc: @apeisa @teppokoivula

I'll start this as a new discussion, idea was introduced in #7. Maybe it ends up on the backlog someday.

When defining access for the first time for a page there's an empty slate to build on. Should we have at least an option to initialize with some defaults?

A couple of different approaches:

  1. Configurable default set of group/access (module configuration)
    • Maybe even an extra option to force this always to ensure a group has access everywhere? On the other hand, if you've got user-admin permission, you're always able to gain access. Thus probably not needed.
  2. Copy inherited access definitions as a starting point
    • Often it's about changing access just a little: add another editor group, revoke view permission from "everyone", etc.
    • Could be a module option not to force anyone down this route

At the moment option 2 feels quite natural and flexible to me. Though not very convenient if there are lot's of inherited definitions and you're trying to get rid of those for a child page.

teppokoivula commented 10 years ago

Your list is a bit funky, but I really like option 2 (or "i"). Makes a lot of sense.

niklaka commented 10 years ago

Sorry, didn't look how it ended up. Tweaked it a little (have to learn more MarkDown, me thinks).

(Got it right after all!)