{"id":4147,"date":"2023-10-27T19:08:23","date_gmt":"2023-10-27T19:08:23","guid":{"rendered":"https:\/\/quebit.com\/askquebit\/?p=4147"},"modified":"2026-01-20T16:00:24","modified_gmt":"2026-01-20T16:00:24","slug":"removing-element-level-security-in-ibm-planning-analytics","status":"publish","type":"post","link":"https:\/\/quebit.com\/askquebit\/removing-element-level-security-in-ibm-planning-analytics\/","title":{"rendered":"How Do I Remove Element-Level Security in IBM Planning Analytics?"},"content":{"rendered":"

Planning Analytics Security<\/strong><\/p>\n

You can create and implement a security scheme<\/strong> in TM1\\Planning Analytics to secure objects and data in your server by defining security groups and clients (users)<\/a>, assigning access permissions to those groups and then assigning users to one or more of the groups. A good security schema will typically consider controlling access at the Element-level <\/strong>– which controls access to cells in a cube that are identified by elements. An example might be preventing a group of users from updating a particular group of general ledger accounts.<\/p>\n

 <\/p>\n

Control Cubes<\/strong><\/p>\n

Planning Analytics uses control cubes<\/strong><\/a> to manage security (as well as other functionality, including performance monitoring) and automatically generates<\/em> the control cubes it needs. To see the control cubes within a TM1\/PA database you can toggle the display in Server Explorer by clicking\u00a0View<\/strong>\u00a0then\u00a0Display Control Objects. <\/strong>If you are using Planning Analytics Workspace<\/strong> (or PAW), and appropriate permissions have been granted to you, all control objects (including security control cubes) are listed under a separate folder and can be expanded within the Databases pane.<\/p>\n

\u00a0<\/strong><\/p>\n

Element Security<\/strong><\/p>\n

Security control cubes apply security privileges for TM1\/Planning Analytics objects to user groups on the Planning Analytics database. Element<\/em> Security cubes apply security privileges based upon elements<\/em>. You can manually create<\/strong> an element security cube using Architect (if you have administrator privileges) by\u00a0right-clicking on a dimension for which you want to define element-level security and then select Security<\/strong>, Create Cell Security Cube<\/strong>. TM1 will then automatically create a security control cube using the naming format }ElementSecurity_ CubeName where CubeName is the name of the dimension that you selected.<\/p>\n

 <\/p>\n

Although there is a programming method<\/em> to create a Cell<\/em><\/strong> Security cube (CellSecurityCubeCreate<\/strong> creates a security cube from an existing cube), there currently is not an equivalent method to create element<\/em><\/strong> security cubes. You can, however, use the ElementSecurityPut<\/strong>() function, and if the }ElementSecurity_ cube does not already exist, Planning Analytics will create it.<\/p>\n

 <\/p>\n

Don\u2019t Want Security on a Dimension?<\/strong><\/p>\n

Regardless of how you chose to create an Element Security cube within your Planning Analytics database, suppose you inadvertently<\/em> create an element security cube on a dimension that should not have it? Or you \u201cinherit\u201d a model that includes element level security on a dimension that no longer requires security at that level?<\/p>\n

 <\/p>\n

The following simple steps can be used to remove and reset security on a specific dimension:<\/p>\n

 <\/p>\n