6.0.0-beta1
9/24/25

[#1375] Impossible to reject all permissions
Summary Impossible to reject all permissions
Queue Horde Base
Queue Version 3.0.3
Type Enhancement
State Rejected
Priority 1. Low
Owners
Requester ancorgs (at) banot (dot) net
Created 02/14/2005 (7527 days ago)
Due
Updated 03/06/2005 (7507 days ago)
Assigned 03/06/2005 (7507 days ago)
Resolved 03/06/2005 (7507 days ago)
Milestone
Patch No

History
03/06/2005 06:46:13 PM Chuck Hagenbuch Comment #4
State ⇒ Rejected
Reply to this comment
I'm comfortable just rejecting this, since to do this basically breaks 
the code model we have and makes it impossible to efficiently check 
permissions. This would require an entirely new permissions API and 
implementation. You can simply design your hierarchy with subgroups to 
do this.
03/06/2005 06:41:19 PM Jan Schneider Comment #3
Type ⇒ Enhancement
State ⇒ Feedback
Priority ⇒ 1. Low
Reply to this comment
This is really an enhancement request, not a bug.
03/06/2005 06:40:40 PM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
Please discuss this on the mailing list because to support this, we 
would require a bunch of changes in the code. Note that we will never 
support denying permissions, but as far as I understood your request 
you simply want to add an "empty" permission set for one user.
02/14/2005 04:08:45 PM ancorgs (at) banot (dot) net Comment #1
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Impossible to reject all permissions
Queue ⇒ Horde Base
Reply to this comment
When setting an individual or group permission is impossible to set a 
user or group to not be able to show, read, alter nor delete.



If none of the 4 checkboxes are marked, the permission is not set so 
you must give at least one privilege to the user/group. This way is 
impossible to totally reject access from a specific user or group to a 
particular module.

Saved Queries