I was wondering why this was not implemented yet, i know that it's a choice to keep access rights and workflow as simple as possible in Umbraco. But a lot of our clients asks or it's possible to set accessrights on Contenttypes.
Most of the times the workaround is to place those particular items under a certain node, and then set the correct rights on it.
But on this moment we have a situation where we have this situation:
-Home ------Node A --------------TypeA --------------TypeB --------------TypeA --------------TypeA --------------TypeC ------Node B --------------TypeA --------------TypeB --------------TypeA --------------TypeA --------------TypeC ------Node C --------------TypeA --------------TypeB --------------TypeA --------------TypeA --------------TypeC
The prefered situation is that editorA only has access to TypeA and also don't want to see Types B and Types C in the tree.
Will this be implemented in V5? The ideal situation is that the Documenttype editor gets an extra Tab with User types and or Users.
As a temporary workaround, is it hard to create a Event handler that makes the "unwanted" items don't show up in the Tree?
Access rights on DocumentTypes
I was wondering why this was not implemented yet, i know that it's a choice to keep access rights and workflow as simple as possible in Umbraco. But a lot of our clients asks or it's possible to set accessrights on Contenttypes.
Most of the times the workaround is to place those particular items under a certain node, and then set the correct rights on it.
But on this moment we have a situation where we have this situation:
-Home
------Node A
--------------TypeA
--------------TypeB
--------------TypeA
--------------TypeA
--------------TypeC
------Node B
--------------TypeA
--------------TypeB
--------------TypeA
--------------TypeA
--------------TypeC
------Node C
--------------TypeA
--------------TypeB
--------------TypeA
--------------TypeA
--------------TypeC
The prefered situation is that editorA only has access to TypeA and also don't want to see Types B and Types C in the tree.
Will this be implemented in V5?
The ideal situation is that the Documenttype editor gets an extra Tab with User types and or Users.
As a temporary workaround, is it hard to create a Event handler that makes the "unwanted" items don't show up in the Tree?
is working on a reply...