Re: [LiveUser] Newbie Q's

Jeff Schmidt wrote:

Then, as far as actually *enforcing/implementing* rights, that is up to me as the developer, correct? LiveUser allows me to ask the questions, who is this user, and does this user have (either directly, or through inheritance from the group it belongs to) right X. My code then decides what to do, if the user has right X or not.

correct.

Is this correct? And how do 'areas' and 'applications' fit into this model? In defining areas and applications, I can have rights that are granted to a user in one area/application, but not another? How does LiveUser figure out what application/area the user is in? Is it based upon what file they are accessing in the filesystem, or do I have to use something like '$objPermAdmin->setApplication($appName);' ?

In your observations you left out one more task that liveuser handles: structuring of rights through structuring your rights you can reduce the amount of rights you have to maintain. areas (group rights) and applications (group areas) let you group rights. this is useful for several things. 1) in the admin panel you can use this meta data to better origanize the interface 2) they can be used for special admin types (atleast areas can atm). areaadmins are special users that get all rights for a given area without having to assign them specifically. this can be really convinient obviously regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07