plainblack.com
Username Password
search
Bookmark and Share
Adding "NotBelongingToGroup"  (#11468)
Issue

Several access problems could be solved, if an Asset would have another group or even two, which excludes view and/or edit the asset.

E.g.: every admin-function could be fine-graded available

or  certain users could be excluded from changing their profile

Comments
preaction
0
4/7/2010 12:56 pm
So there's an asset property for "Group To View" and for "Group To Not View". How are conflicts handled?

Or are we talking like subtracting users from a group in the group configuration:

Group A contains everyone in Group B that is not also in Group C.

Either way you're talking changes to the fundamentals of WebGUI with not-minor performance hits.

Right now I don't see how this can be accomplished. What do you really need?
martien
0
4/7/2010 5:31 pm
[quote]What do you really need? [/quote]
The easiest example:
I need one registered guest user with all the rights of a registered user, but cannot change it's profile and/or has no access to op=displayAccount and the following functions (Profile, Inbox etc.)
preaction
0
4/8/2010 2:42 pm
The easiest way would be to override the appropriate Account plugins to edit the canView method to disable that user, as well as the Auth->displayAccount method to call the correct canView method.

This could also be made into an RFE
Details
Ticket Status Pending  
Rating0.0 
Submitted By martien  
Date Submitted2010-03-11 
Assigned To unassigned  
Date Assigned 2012-02-12  
Assigned By  
What to improve? WebGUI Beta  
URLrfe/request-for-enhancement/11468
Karma
Difficulty 1  
Karma So Far0
Karma Rank0.00
Keywords
Ticket History
4/7/2010
5:31 PM
Pending martien
4/7/2010
12:56 PM
Feedback Requested DBell
3/11/2010
6:32 PM
Ticket created martien
© 2012 Plain Black Corporation | All Rights Reserved