A Teradata role may be denied access to one or more cubes of a cube schema. Additionally, a role can be denied access to a specific hierarchy.
You cannot control access to cube measures using Teradata BI Repository security. To prevent a user role from accessing certain measures, create a cube with fewer defined measures.
Security policy changes take effect when the schema publishes to the Teradata BI Model Repository.
For a dimension to be visible, a role must have access to the cube to which it belongs. A Teradata role might then be denied access to a specific dimension within that cube.
For a hierarchy to be visible, a role must have access to the cube dimension it belongs to. A dimension can have more than one hierarchy. For example, a Time dimension might have Calendar Year and Fiscal Year hierarchies.