View source | Discuss this page | Page history | Printable version   

Screenshot:Role

This article is protected against manual editing because it is automatically generated from Openbravo meta-data. Learn more about writing and translating such documents.
Back button.png   Back to Screens_Reference


Contents

Role

The aim of a role is to group user/s depending on what parts of Openbravo they are allowed to access to and therefore to work in.

Role

Role window allows to review, create, configure and maintain the roles to use in a given client.

Org Access

Org Access tab allows to define the organization/s to which a given role will have access rights to.

User Assignment

User Assignment tab allows to add users to a given role.

Window Access

This tab lists and/or allows to add the windows to which a role will have access to.

Tab Access

Defines whether a tab is editable or read only for a concrete role.

Field Access

Defines whether a field is editable or read only for a concrete role.

Report and Process Access

This tab lists and/or allows to add the reports and processes to which a role will have access to.

Form Access

This tab lists and/or allows to add the forms to which a role will have access to.

Widget Class Access

This tab lists and/or allows to add the widget classes to which a role will have access to.

View Implementation

View implementation tab allows to select customized views.

Process Definition

Grants access to Process Definition. By default, access to process definitions in a window (invoked from a button), is inherited from the permission to the window. To revoke this inherited access and manually decide case by case which are the accessible processes, it is necessary to define a "Secured Process" Preference (at system level or for that specific window) with "Y" as value.

Role Inheritance

Allows to define an inheritance for a role. An inheritance is a relationship between two roles: if role A inherits from role B, that means that all the permissions that role B has for different application elements like organizations, windows, reports, processes, widgets etc. will be automatically inherited by role A, allowing it to access those elements in the same way as B. It is also possible to define an inheritance hierarchy, i.e., a role can inherit from different roles, and the priority (order) to inherit the permissions is defined by the sequence number. This means that if two inheritances have accesses in common, the accesses of the inheritance with lower sequence number will be overridden with the accesses of the inheritance with higher sequence number.

Back button.png   Back to Screens_Reference

Retrieved from "http://wiki.openbravo.com/wiki/Screenshot:Role"

This page has been accessed 6,309 times. This page was last modified on 3 January 2022, at 01:44. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.