+38 (067) 282-63-66

office@bitimpulse.com

  • Ua
  • Ru
  • En

Creating a BAT-role

To create and manage the roles in BAT you have to use “Roles” tab:

In the list of roles you will see the role “All Users”. This is a built-in role that includes all report module users. Thus, if you change the settings for that role, the changes will affect all users.

Let’s create a new role in BAT. It can be done in three ways:

  • Press the button on the toolbar:

  • Press the button under the roles list:

  • Select the corresponding item from context menu:

Fill in the name of a new role and check the option “Use for security” (this will enable us to set the access permissions for dimension members for the users in role):

Press the «Save» button and you will see the new role in the roles list:

Select the newly created role in the list and at the bottom of the form switch to the “Restrictions” tab:

To set the visibility restrictions on hierarchies and measures from a cube for this role, select that cube in the list and press the «Add / Edit…» button:

In the appeared window in “Hierarchies” tab uncheck the “No restrictions” check box to see the list of hierarchies. In this list you can select the hierarchies, visible for this role:

First, press the «Select All» button, and then uncheck all hierarchies under the “Customer” dimension:

Thus, you banned the users included in Test Role from seeing the whole dimension “Customer”.

On “Measures”, “KPI” and “Calculations” tabs you can similarly set the visible measures, KPIs and calculated measures, respectively.

Press «OK» to save your changes. Now in the list of restrictions you will see that there are restrictions set for the cube Adventure Works:

On the “Permissions” tab you can set the access rules for dimensions members for the role. This is done exactly the same way as you did it for report module users, so we are not going to describe that process once again.

The “Parameters” tab is used to quickly set up the access rights on dimensions members for a big group of users. We will review this process in one of the following chapters.