A Permission Role represents a group of users who have their permissions restricted to some extent. Each role inherits permissions from its parent role, the role role.admin is the ancestor of all roles. The role.pro is a child of role.admin. So if a feature is restricted in role role.admin it will also be restricted in all the other roles.

h2(#roles) Roles

  • role.Admin:
    The ROB-EX Admin user has permission to edit the plan and edit other users.
  • role.Pro:
    The ROB-EX Pro user has permission to edit the plan.
    Does not have permission to edit other users.
  • role.Prolimited, role.Standard, role.Standard-limited, role.Light-limited:
    The various roles like light-limited, and pro-limited are by default identical to their non-limited counterpart. The limited variants exist only to allow for a larger degree of customization in custom/roles.xml.

    Note that the role.Standard-limited provides Planner rights in ROB-EX Desktop Planner.
  • role.Light:
    The ROB-EX Light user has permission to read/write the following fields in the plan:
    - Operation description
    - Operation customText1-4
    - Production order description
    - Production order customText1-8
    But only for operations assigned to a production order. Master routes or master operations cannot be edited.
    Does not have permission to edit other users. Have fewer permissions than the Pro user.
  • role.Viewer:
    The role provides view only access for ROB-EX Desktop Viewer and {RBX-WEB-VIEWER.
    The user will not have permissions to change anything in the plan or edit any configuration related to other users. The user is able to change a few per-user preferences.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment