To allow access to Teradata BI Repository, identify and specify one of the Teradata Database roles, such as TBI_SALESCUBE_ALL, into the cube schema. Create the role within Teradata Database first. Validation verifies all mapped roles exist within the chosen Teradata Database.
Each Teradata Database role mapped into the Schema Tree View defaults to having full access to the entire schema after publishing the schema. Unless you want them to see the entire schema (all aspects of all cubes), restrict that role in Schema Tree View to just the cubes or other OLAP objects they should have access to.
If a use has multiple roles with conflicting rights on a schema, cube, dimension, hierarchy, level or members of a level, the least restrictive security is the default, combining access for all roles together.
Mapping a role provides role access to a particular schema.
- Click to open a schema.
- In Schema Tree View, click Business Intelligence Data View.
- Select the Security tab. The Schema Editor Properties pane displays a table with all roles in the database. Beside each role is a check box indicating if the role is mapped into the schema.
-
Click the Grant check box to map a role into the database.
Each checked role is immediately added to the Tree View under the Security folder.
The check boxes grant the mapped role to the schema, but not to any schema element. Access is granted to individual levels, hierarchies, dimensions, and cubes in the sections Defining Cube Security and Defining Level Security. -
Uncheck each role to be unmapped from the schema.
If a role is removed from the Teradata Database system, it is no longer available in the Security tab.