TM1 Contributor - How to restrict access for specific items
Posted: Thu Feb 04, 2010 9:17 pm
Hi,
I am trying to figure out what is the best way to achieve the following:
It's a quite common scenario and in EP we used Access Tables for that. Let's say you have a list of 100 employees and 20 cost centres. Cost centres will be the Approval hierarchy (eList). You want to make sure that when cost centre manager opens it's cost centre in Contributor the list of employees is filtered to show only the employees that belong to that cost center. Same concept could happen with Products, etc.
What I have tried so far:
I created rule based security that apllied "None" to the relevant "Cost center <> Employee" combination. Security works, but it doesn't hide the irelevant employees. You just can't see and enter data against them. But I don't want to see them at all.
Ideas: Create dynamic subsets and link them to the particular cost center. Not 100% if that is possible though.
This must be a common concept in the TM1 world, so I am interested in how you guys usually approach this.
Thank you!
Carsten
I am trying to figure out what is the best way to achieve the following:
It's a quite common scenario and in EP we used Access Tables for that. Let's say you have a list of 100 employees and 20 cost centres. Cost centres will be the Approval hierarchy (eList). You want to make sure that when cost centre manager opens it's cost centre in Contributor the list of employees is filtered to show only the employees that belong to that cost center. Same concept could happen with Products, etc.
What I have tried so far:
I created rule based security that apllied "None" to the relevant "Cost center <> Employee" combination. Security works, but it doesn't hide the irelevant employees. You just can't see and enter data against them. But I don't want to see them at all.
Ideas: Create dynamic subsets and link them to the particular cost center. Not 100% if that is possible though.
This must be a common concept in the TM1 world, so I am interested in how you guys usually approach this.
Thank you!
Carsten