Change in dimension hierarchy security

Planning Analytics 2.0.9.5 introduces an enhancement to hierarchy security.

You can now define security for dimension hierarchies independent of the parent dimension in the }DimensionSecurity control cube.

In previous version of Planning Analytics, dimension hierarchies inherited security from the parent dimension. There was no need to explicitly define security for an hierarchy in the }DimensionSecurity control cube. For example, here the North America user group inherited Read access for all hierarchies of the Model dimension, while the South America user group inherited Reserve access for all hierarchies of the dimension.

Hierarchy security definitions pre-2.0.9.5

As of Planning Analytics 2.0.9.5, hierarchies no longer inherit security from the parent dimension.

Important: If you want a user group to have access to a dimension hierarchy, you must explicitly define hierarchy security in the }DimensionSecurity control cube. If you do not define security for a user group to an hierarchy, members of the user group cannot see the hierarchy in Planning Analytics.

You can assign hierarchy security equivalent to or lower than the security defined for the parent dimension. A user group cannot have higher security access to a hierarchy than to the parent dimension.

Here's an example of how you define hierarchy security in Planning Analytics 2.0.9.5 and later:

Hierarchy security definitions 2.0.9.5 and later

Each hierarchy has security explicitly set for all user groups. Note that a blank cell is equivalent to None security.