TM1 Forum

Sorry for foolish question, i'm new.
I write cell security. If i write rule in :

['element1']='READ'; (for example time dimension)
['element2']='WRITE'; (for example some user group)
[]='READ';

['ELEMENT3']=UNDER SOME CONDITIONS 'WRITE','READ';

Means this that element1 is every time read?, Element 2 every time write, element 3 read or write, rest of the cube is read? Regardless order how rules are writen?

But what about intersection in cell element1xelement2?

sun wrote:Sorry for foolish question, i'm new.
I write cell security. If i write rule in :

['element1']='READ'; (for example time dimension)
['element2']='WRITE'; (for example some user group)
[]='READ';

['ELEMENT3']=UNDER SOME CONDITIONS 'WRITE','READ';

Means this that element1 is every time read?, Element 2 every time write, element 3 read or write, rest of the cube is read? Regardless order how rules are writen?

But what about intersection in cell element1xelement2?

Cell security can be very hard to maintain even for experienced TM1 Administrators, so I would take it back to the drawing board and see whether you could achieve your desired security by using element applied security instead of cell level.


As to your question here:

If the first statement in a rule applies to a cell (we will call it cell X)
The second statement in a rule also applies to cell X

The first rule will be enacted and the second rule ignored (for that cell)

So the intersection of Element1 and Element 2 in your example would be 'READ'.

Thank you for replay.
SO in this case, as i wrote... Becasue i have

[]='READ';
and then

['ELEMENT3']=UNDER SOME CONDITIONS 'WRITE','READ';

Second rule has no effect?

tnx

Regards

sun wrote:Thank you for replay.
SO in this case, as i wrote... Becasue i have

[]='READ';
and then

['ELEMENT3']=UNDER SOME CONDITIONS 'WRITE','READ';

Second rule has no effect?

tnx

Regards

You are correct.

[]='READ'; renders any subsequent statements useless.