Expand my Community achievements bar.

Internal Creative Private Proofing Workflow


Level 2
We have an internal proof workflow built for our creative team so client cannot view the proofs, we use this for creative collaboration, CD/ACD approvals, etc prior to client reviews. It's a great tool for this, however we are having two issues: 1) We cannot set a folder up to be private 2) We have to manually delete "inherited permissions" in the sharing settings of every proof doc once we've generated the proof Is there any way to set up a standardized workflow template process or setting to address both or either of these? Melanie Hatfield Whirlpool Corporation

Topics help categorize Community content and increase your ability to discover relevant content.

1 Reply


Level 7
My guess is that your proofs are inheriting things from the project / program / portfolio, this is probably working as intended. My best suggestion would to be to set up a private portfolio / program which is not shared with a lot of people and do the proofing there, you can always 'move' a document from one project to the other when you need outsiders to view it. Richard Carlson Behr Process Corporation