Eric D. Schabell: Red Hat JBoss BPM Suite - Understanding User Role Access

Tuesday, May 27, 2014

Red Hat JBoss BPM Suite - Understanding User Role Access

When using the JBoss BPM Suite or JBoss BRMS products, you have a choice of roles available to assign users.

These roles will determine what aspects of the provided workbench will become accessible to your users.

For example, you might not want your business analyst to be able to perform administrative functions on the project as a whole and remove assets or critical parts of your business rules projects?

Can you imagine that a user of the financial project you are designing to sell bonds could maybe adjust the rules so that a friend would get 80% interest on her newly purchased savings bond?

Not to worry, the products provide out of the box access roles predefined for ease of use.

Admin role
This role is meant to provide any user given it with full and complete access to all areas of the product.

Developer role
This role provides full access, except to the Administration perspective where you manage project and organizational setup.

Analyst role
This role provides the same access as the Developer role, except for no access to the asset repository and deployments.

User role
This is the role designed for the user of your system who is only allowed to manage processes, tasks that are generated for them, and view the created or provided reporting dashboards.

Manger role
This is the most restrictive role where we allow the user to view Business Activity Monitoring data in the form of provided or created reporting dashboards.

It should be noted that you can create other roles that are usually related to the assignment of user tasks, but these should be used in conjunction with one of the above defined access roles and do not supersede them.

We hope this overview gives you a better idea of what you can expect to find when you login using one of the above roles with the JBoss BPM Suite.