Improve Role Inheritance

Description

Actually iDempiere supports role inheritance - a role can be composed by included roles, and in such case it inherits the configuration for menu access options and for org access.

This idea is to extend this feature to be able to define master roles in System client, the master roles in System client can have menu access options (but cannot have org access options, because orgs are not available on System).

  • The Client (not System) roles can inherit from System roles the access options, and additionally we want to enable configuring exceptions for the roles:

  • adding specific access not including in master role
    or

  • disabling (adding and inactivating) options included in the master role

  • The inheritance must work just for menu items, but not for org, data or documents. (please evaluate if it can be extended for documents too)

  • We need to add a flag in role to indicate that it is a "Master Role". Users must not be assigned to Master Roles.

  • The list of "Included roles" must show only "Master Roles"

  • Check the ordering of the process list on Process Access tab to make it logical.

Environment

None

Attachments

6

Activity

Show:

Carlos Ruiz October 24, 2012 at 4:48 AM

Juliana Corredor T. October 20, 2012 at 7:13 AM

restrict use of master roles

Carlos Ruiz October 20, 2012 at 4:40 AM

Juliana Corredor T. October 17, 2012 at 4:40 AM

When a Master role is not active, doesnt allow to inherit permissions

Carlos Ruiz September 28, 2012 at 12:23 AM

Fixed

Details

Assignee

Reporter

Priority

Created August 9, 2012 at 7:45 AM
Updated January 18, 2016 at 10:36 AM
Resolved October 24, 2012 at 4:48 AM