Re: [Phpwebsite-developers] Storing user level options for modules

[clayton c. <cc...@ca...>]

Jason,
  im working on specs for security (actually access control). we can handle
security in a way that does not require each table to have an additional
security related table. check out Todd's website for the translations i did
of ACS's 3.x permission system. it handles security in a much more granular
way than just the "seclevel" way.

    the benefit of this approach is that the module writer simply has to
define a set of permissions for the module (maybe in a module XML
description file), and the security admin code can handle everything else in
a generic way. In other words, the module writer can simply write the module
and not have to worry about implementing his/her own code for setting up
permissions.

    while on the subject, how are we segmenting admin "levels"? my thought
is site admin, group admin, maybe module admin, and if we decide to do
multiple sites per install, "super" admin