[Tickets #2117] Make Horde Permissions inheritable
bugs@bugs.horde.org
bugs at bugs.horde.org
Tue Oct 25 11:01:02 PDT 2005
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=2117
-----------------------------------------------------------------------
Ticket | 2117
Updated By | Chuck Hagenbuch <chuck at horde.org>
Summary | Make Horde Permissions inheritable
Queue | Horde Framework Packages
State | Accepted
Priority | 2. Medium
Type | Enhancement
Owners |
-----------------------------------------------------------------------
Chuck Hagenbuch <chuck at horde.org> (2005-10-25 11:01) wrote:
> 1) How to make changes to existing permissions - I like the idea of
> an "Apply to Children" button.
Having this makes sense to me, though it's a different thing than this
ticket (mostly).
> 2) How to determine permissions for new nodes - inherit from parent,
> this is the way most permission systems operate (filesystems come to
> mind), so yes, I think admins would wrap their heads around this
> quicker.
I just want to say that I don't like the idea of some permissions inheriting
and others not. I think we should either have no inheritance, or everything
inherit. I know that going to everything inherit will cause some transition
pain, but I think it's much saner in the long run.
More information about the bugs
mailing list