From: ExsonQu <hex...@gm...> - 2013-12-05 07:27:32
|
* Dear all,* Thank you for your great feedback. There are several kind of authority method exists such as: 1. Tokens for page authority. 2. Tokens for special item such as token 12 for price. 3. Control by roles and person together. Such as salesman and petty cash. 4. Control by person, such as bank transaction accounts control. If we use tokens as the unique way, we have to face two problem: 1) One token can only provide Yes or No flag. If we have more than 2 choice, we have to add other limit that set a token range to control those option. 2) We cannot solve the problem of initiator->Confirm->Approve management chain. Maybe just because of I'm too stupid to find a way out. So I think token itself is not enough. We have to another standard way to solve at least above problem---provide more precision control method to more than 2 choices and have a simple and powerful approval chain. Thank you again. Looking forwarding more advice from you. Best regards! Exson phildaintree wrote > Hi Ricard/Exson, > > I think the token system now has a lot of flexibility in it. Users can > set up new tokens, new roles, and change the tokens required for each > script. This is complex, but generally a once only job. It is > perfectly possible to have one role per person in an organisation if > that is the way the company wants, so effectively we can now do > security by role, or by person. > > I like the idea of narrowing down the GL codes that a user can see, > and this is something we get asked for a lot. I like the way Ricard > approached this with petty cash, and would like to see that extended > throughout webERP. > > Thanks > Tim -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Shall-we-find-a-another-regular-way-to-manage-authority-tp4657044p4657048.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |