Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

4.2. Managing Users

4.2.1. Role-Based Permissions
Copy link

JBoss Enterprise BRMS uses role-based authorization to assign permissions to users. By default, role-based authorization is disabled and must be enabled (see the JBoss BRMS Getting Started Guide for details). If role-based authorization is not enabled, all users have full administrative privileges.
The roles that can be granted are admin, analyst, and package permissions.
Admin Permissions
Users who have been assigned the admin role have complete access to all areas of the JBoss Enterprise BRMS Platform and can manage other user's permissions.
Analyst Permissions
Analyst permissions are intended for the users responsible for maintaining rules. Both developers and business analysts should be granted analyst permissions. Analysts permissions are associated with categories. This makes it possible to manage which rules users are granted analyst permissions for.
In addition to the analyst permissions, it is also possible to grant users Analyst read-only permissions. This allows the user to view the rules in a category, but it does not allow users to edit or change them.
Package Permissions
There are three types of package permissions:
Package Administrator
The package administrator permission grants full control over the specified package, including the right to deploy it. The Package Administrator permission does not grant any administrative rights to any other part of the JBoss Enterprise BRMS Platform.
Package Developer
Package developer permits users to create and edit items within the specified package. This includes being able to create and run tests but does not include the right to deploy the package.
Package Read-only
The package read-only permission grants read-only permissions to a package allowing a user to view the package.
JBoss Enterprise BRMS does not manage the identity of users. Only users who have been assigned as BRMS users will be visible in the user interface, and these users must be added manually.

Copy link

Report a bug

4.2.2. Adding a New User
Copy link

Procedure 4.4. Add a New User to BRMS

  1. Select Administration from the navigation panel, then select User Permissions.
  2. Add user mapping by clicking on the Create new user mapping button. Type the username into the dialogue box that appears, and then click OK.

    Note

    The username that is specified for the role must match a username in the authentication service or it will not work.

Copy link

Report a bug

4.2.3. Managing User Permissions
Copy link

Procedure 4.5. Manage User Permissions

  1. Select Administration from the navigation pane, then select User Permissions.
  2. Click Open next to the username.
  3. Assign user permissions by clicking the plus icon and selecting the appropriate permissions from the Permission type drop-down menu. Click OK to confirm.

  4. Remove User Permissions

    Remove user permissions by clicking the minus icon next to the permission being removed, and click OK to confirm.
Users assigned the admin role will be able to modify the roles and permissions of others.

Copy link

Report a bug
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat