From: Rafael C. <raf...@gm...> - 2013-12-09 16:16:46
|
Hallo, My two cents: I have seen in other projects: 1. Group-access, sub-group-access, sub-sub-group-access --from general access to specific access--. The sub-groups inherit the attributes of groups; The sub-sub-groups inherit the attributes of sub-groups. It is a kind of pyramid of access rights. E.g. Joomla! 2. Group-access and individual-access --general access for groups, specific access for individuals--. The individuals inherit the attributes of the groups to which they belong. E.g. EGroupware. Personally, I like the EGroupware way. In both cases, I used the group-access as the Department attributes (general access rights for all the people who belong to a department). I think we could use the current structure, with little modifications, to adapt to any of them. What is critical is to distribute access-rights variables by all scripts, and then to fill an array of access rights. Regards, Rafael. 2013/12/5 ExsonQu <hex...@gm...> > *Hi, Jo,* > > You're right that we should have a convent for access control. > And granularity is just one point of the discussion, another one is the > approval control or approval processes management. I hope we can set a rule > for that. > > Thanks and best regards! > > Exson > > > > -- > View this message in context: > http://weberp-accounting.1478800.n4.nabble.com/Shall-we-find-a-another-regular-way-to-manage-authority-tp4657044p4657052.html > Sent from the web-ERP-developers mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Sponsored by Intel(R) XDK > Develop, test and display web and hybrid apps with a single code base. > Download it for free now! > > http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > |