I can see the alternate hierarchy is in }DimensionSecurity cube. I thought I can put some securities on them but apparently it doesn't work in PAW. Users with NONE access can still see the use the hierarchies normally. 
Is IBM planning to put security control on alternate hierarchy? If not, the "security" of alternate hierarchy is with dimension? i.e. As long as the user has READ access on dimension, then he can use alternate hierarchy without any issue. I tested the case and seems to work in this way.

------------------------------
mvp morgan
------------------------------

#PlanningAnalyticswithWatson

Hi Morgan,

Currently, hierarchies do not have their own security.  This might be something we add in the future.  Security access (NONE, READ, WRITE, ADMIN) is only applied on the parent dimension, even though it does seem like you can apply it to the hierarchies in the }DimensionSecurity cube.  Although we do not support separate security on hierarchies, I think there was an issue where if at least READ access security was not set for a hierarchy, then the user could see the hierarchy and it's members, but could not access the subsets under that hierarchy.

Yes, IBM would like to see security on hierarchies as a feature in a future release of TM1 database!

------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------

Hi, Stuart

Thanks for the confirmation. Yes, that would be good, which will give different users different hierarchies for reporting. For now, as I tested the element security cube still works as it can control what elements can appear in alternate hierarchies although users still can see the hierarchy names.

------------------------------
mvp morgan
------------------------------

Original Message:
Sent: Mon September 21, 2020 07:23 AM
From: STUART KING
Subject: Security on Alternate Hierarchy?

Hi Morgan,

Currently, hierarchies do not have their own security.  This might be something we add in the future.  Security access (NONE, READ, WRITE, ADMIN) is only applied on the parent dimension, even though it does seem like you can apply it to the hierarchies in the }DimensionSecurity cube.  Although we do not support separate security on hierarchies, I think there was an issue where if at least READ access security was not set for a hierarchy, then the user could see the hierarchy and it's members, but could not access the subsets under that hierarchy.

Yes, IBM would like to see security on hierarchies as a feature in a future release of TM1 database!

------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------