AnsweredAssumed Answered

Some rights are inherited, some are not... is that correct?

Question asked by Brian Dalton on Mar 5, 2012
Latest reply on Mar 6, 2012 by Brian Dalton

I have Mfg users that are only supposed to be granted Read Contents access to files once they reach the 'Released' state.  I discovered that if an Engineer moves a 'Released' file to the 'In Revision' state, the Mfg users can still see them, because the Read Contents right is inherited by all subsequent states, unless I set 'Ignore permissions' so that the right is not inherited.


This seemed strange to me, because it doesn't work that way with 'Check out files' rights.  My Engineers have Check Out rights when they create their files and they retain that right until the file reaches the 'Released' state.  In that state, Check Out rights are not granted - however - I have not set 'Ignore Permissions' at that state, so the Eng users should still be able to check the files out.... but they can't.


So, I'm wondering if that's the way it's supposed to be?  Are some workflow state rights inherited by default and others are not?  I don't remember reading anything about different rights having different 'inheritability' but I could have missed it.


Is there a list of workflow state rights with indications of which are inheritable and which are not?