BAM Tree Menu Rights

What is BAM Tree Menu Rights?

The BAM Tree Menu rights specify the nodes of the tree structure in the BAM Report. The tree structure is shown below.

AVEVA Work Tasks security provides the BAM Report Rights to control or restrict the access to these tree nodes (either privilege or restrict) in the BAM Report.

How to Access BAM Tree Menu Rights?

To access or set the BAM Tree Menu Rights, the user must have administrative privileges.

To view the BAM Tree Menu rights, follow the steps given below:

1. Login as an Administrator user.

2. Select Reports from the Enterprise Console menu.

   The BAM Tree Menu Rights appears.

Purpose

AVEVA Work Tasks provides the BAM Tree Menu Rights to control the tree nodes (either privilege or restrict) in the BAM Report. In the BAM Tree Menu Rights, only those nodes for which a user has permission will be displayed in the BAM Report while the user is accessing the BAM Report.

Scenario

Scenario Description: Restricting the user from viewing some nodes in the tree structure of the BAM control.

Business Scenario: This scenario describes how to prevent the contributor user from viewing some nodes in the tree structure of the BAM control. Here, the Administrator user can restrict the contributor user from viewing the Workflow Statuses and Workflow Instances nodes of the tree structure in the BAM Control.

Roles: To understand this scenario effectively, assumed that there are two users in a repository. The first user belongs to the Administrator security group and the other user belongs to the Contributor security group.

3. admin  - Will have Administrator access rights.

4. UserC - Will have Contributor access rights.

The following table depicts the users and their security groups:

Overview

Both the admin and UserC (Contributor) are able to see all the nodes in the tree structure of BAM Control.

The admin (Administrator) wants to restrict UserC (Contributor) to viewing some nodes in the tree structure of BAM Control. The same is depicted in the following table:

Scenario Solution:

To achieve the same, perform the following steps:

5. Login as the Contributor user. Here, login as 'UserC'.

   Before the security settings, the Contributor user can see all the nodes of the tree structure in the BAM Control. As mentioned above, the user must be an administrator to configure the security settings. As the admin user belongs to Administrator security group, this user can set the security settings to restrict the UserC to viewing some of the nodes in the tree structure in the BAM Control.

6. To restrict the UserC to viewing some of the nodes in the tree structure in BAM Control, login as an administrator user. Here, login as 'admin'.

7. Click Repository Settings > Advanced Settings > Manage Security Groups. You will be redirected to the Security Group list.

8. As the 'admin' user wants to restrict the contributor user, either select 'Contributor' and click Actions > Edit or right click 'Contributor' and then select Edit from the context menu.

9. A pop-up window appears with the assigned security rights. Click the Set BAM Rights link. Another pop-up window appears to set the BAM Rights.

10. Expand the BAM Tree Menu Rights.

11. The administrator user wants to prevent the other user from viewing the Workflow Statuses and Workflow Instances nodes under the Dashboard node. Unselect the Check for Inclusion check box. It means the selected rights should be excluded (restricted). So select the Workflow Statuses  and Workflow Instances nodes under the Dashboard node.

12. After selecting the nodes to restrict, click Save. The window will be closed and you will be redirected to the security rights page. Click Save.

13. The Synchronization dialog box is displayed. Click Yes to synchronize the changes to the below level.

14. A message stating that “Security Group has been modified successfully” will appear. Click OK. Now the admin user has restricted the UserC (contributor) from viewing Workflow Statuses and Workflow Instances nodes of the tree structure in the BAM Control.

15. To check the same, login as a user who belongs to the contributor security group. Here, login as 'UserC'.

16. Select Reports from the Enterprise Console menu to access the BAM control. Observe that the Workflow Statuses and Workflow Instances nodes are not visible in the tree structure of the BAM control.