Re: [Product-Developers] Some way to avoid propagating permissions?

2011-12-19 Thread Mikko Ohtamaa
in my intra-net there are certain folders that only I should be able to change. Therefore, I created a new workflow state 'static' in which only I have Add permissions, and applied this workflow state to these nodes. However, these permissions propagate to child nodes that have the 'inherit

Re: [Product-Developers] Some way to avoid propagating permissions?

2011-12-19 Thread Maarten Nieber
I agree: add a placeful workflow policy via Site Setup then on the folder in question use the State-Advanced menu to add that policy on the current folder. You will be able to select your static workflow for the current folder and any other workflow you want for children of the current folder.

Re: [Product-Developers] Some way to avoid propagating permissions?

2011-12-19 Thread T Kim Nguyen
Ah, sorry I misread. I understood you had created a different workflow that had only the static state. Kim On Dec 19, 2011, at 8:27 AM, Maarten Nieber maar...@usecm.com wrote: I agree: add a placeful workflow policy via Site Setup then on the folder in question use the State-Advanced

Re: [Product-Developers] Some way to avoid propagating permissions?

2011-12-19 Thread Sean Upton
On Mon, Dec 19, 2011 at 7:27 AM, Maarten Nieber maar...@usecm.com wrote: But the problem is with the permissions, not with the workflow, right? If I put my parent node in the 'static' publication state, then the child nodes which have inherit permissions' will acquire the permissions