Finance Role - Sub division of financial Role Required

[Ali_Muhamamd_Nizaman]

Dear Team,

1. Can i create sub roles within per-define finance Role??? for example i have three users in finance department and i want to give different restriction levels within finance Role?

2. I create a user and assign him finance role even though system is showing me all menus like stocks , products , orders … these links shouldn’t appear for financial user? so plz guide , did i make some thing wrong while assigning the rights.

Please help

[jmiranda]

At the moment, the finance role is only used to permit users to view and edit pricing and inventory value data.

@Ali_Muhamamd_Nizaman

for example i have three users in finance department and i want to give different restriction levels within finance Role?

Can you specify what those restriction levels might be and what they would allow the user to see or do? We are planning to refactor the security module in the 0.9.x release so it would be great to get feedback on how you’d expect it to work.

@Ali_Muhamamd_Nizaman

I create a user and assign him finance role even though system is showing me all menus like stocks , products , orders … these links shouldn’t appear for financial user?

The finance role is a supplemental role, similar to the notification roles. It only adds a small amount of functionality (view / edit pricing info) to one of the primary roles (Superuser, Admin, Manager, etc).

In general, we don’t hide menu items based on role because we want the user experience to be consistent across roles. Instead we display an “Access Denied” message indicating that the user does not have access to a particular feature. This was based on UX research on access roles. I’ve included a non-exhaustive list of resources re: this debate.

• https://ux.stackexchange.com/questions/334/is-it-better-to-prevent-a-forbidden-action-or-display-an-error-explanation-messa
• https://stackoverflow.com/questions/371921/should-unauthorized-actions-in-the-ui-be-hidden-disabled-or-result-in-an-error

With that said, this approach is debatable. We’d probably be ok with making this a configuration option 1) show access denied vs 2) hide features entirely.