Michael, > I originally thought rm-level auth was a bad idea since you should group > the run modes into an application module that is used by the same type > of user. I can however see why you might want to group several run modes > that deal with the same data type together... but I'm still not totally > convinced. Anyone else have any thoughts on this? I just always do > module level auth and then never have to worry about securing individual > run modes, just the app module.
I've running a rather large multi-module system all based on C::A. My admin user interface allows me to create a permissions file to allow access to entire modules as well as individual aspects of that module. i.e. Reporting Module [ y / n ] -> See General Reports [ y / n ] -> Download As Excel [ y / n ] -> See Detailed Reports [ y / n ] -> View Geo-plot Report [ y / n ] For various reasons, some of these run-modes may not be accessible to the client (or certain admin users within the client's organization). Therefore, rm-level auth is nessecary for me, otherwise I'd have to split each of the rm's off into their own module and I'd have more modules then I know what to do with (which is currently almost the case anyways :p ) --- Steve Comrie --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
