IBM Planning Analytics Tips & Tricks: Cell Level Security Defaults

October 1, 2019

Did you know that you can have TM1 / Planning Analytics security always use your cell security definitions … even when the security definition cell is blank?

Values in a cell security cube override all other security. But if an intersection in the cell security cube is blank then, by default, other definitions such as cube, element and dimension security will be used.

In TM1 version 10.2, a new cube was created that allows you to override this approach. The cube is called }CubeSecurityProperties and it contains a setting called CELLSECURITYDEFAULTVALUE. The initial setting is blank, which allows the standard approach of “use the other definitions” to still apply. However, you can change this approach by populating a value into the cube.

If you change the value in the }CubeSecurityProperties cube then all cells with an empty value in the cell security cube will use that setting. Values in the }CubeSecurityProperties cube can be set to NONE, READ or WRITE.

In the example below, blank cell security intersections will be set to READ

IBM Planning Analytics Tips & Tricks: Cell Security Defaults

When using this, be sure to think about any ripple effects associated with your existing security. For example, if you set a cube to READ then you will need to explicitly set cells to NONE that you don’t want users to see (whereas it may have already defaulted to NONE before the cube was populated).

This approach gives you more options to determine how cell security interacts with the rest of your security model.

IBM Planning Analytics, which TM1 is the engine for, is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!

Author

Lee Lazarow

View all posts