TM1 Forum

Hello All,

We have a strange requirement from client as what they asked for:

To Create 4 views, each for three roles as BI , AM and FM and one everything view which will contain all fields available in Cube. BI, Am and FM cube views will list out specific fields meant for these three roles.

Now the requirement is like that if BI user will login into Contributor, he will be able to see BI view along with Everything view and in BI view he/she must be able to manipulate field he/she will have write access of. But in everything view, it should be all READ access for all fields even for fields for which BI has write access in BI view.

So my questions:
1. Is it possible to implement view level security in Contributor or in Architect?
2. I know it is not possible to provide read and write access simultaneously on same field even though by creating diff grps, so just wanna know is there any workaround for it.?

Any help would be really appreciated.

Thanks,
Manoj

I'm afraid there is no concept of 'view level security' in TM1.
But thinking outside the box a bit...
If you set up a set of shadow elements and populate them with rules (and feeders) then the ruled elements will be RO and the elements they point to will be RW. Would that help?

Thanks a lot David..

This will really help us.

Also is there any way we can retrict access of views in Contributor or Architect?

Anybody anyidea?

Thanks,

As per my post, you secure access to data, not to views. Remember users can create their own views if they wish. But you can do a lot with cube and element security - and if you want to get intricate, cell level security (but this is best done with rules IMO).