Restricting Visibility to Document Proofs from Marketing Until Ready to Review

Hi @jennajurgella1 

It's very dependant on sharing settings, inherited permission etc, as you know.

I don't know if the following can fit your set-up but I suggest you to have a look at this Acces Level Option:

I remember using it once to allow Docs to be only visible by their creator, and shared only with others through Proof. One who's part of the proofing workflow will be able to access it

Maybe worth a try? 

Are you adding users to the proof for approvals as you create it? If so, it will be challenging to control, as they receive an email and notification asking them to approve. 

If you are generating the proof and adding the approvals later, you could do this as an option:

Create a folder in your Project, Task, Issue, etc. Then turn off the inherited permissions inside that folder and load the document there. The folder will stay hidden from users. Then, when ready, move the document out of that folder into another, or the general documents area, attach your approval, and it will be ready and proper sharing permissions will be intact.

I have this setup at our template level, so any time the template is used, the folder permissions are set. Documents can be moved in and out of the folders as needed. 

@jennajurgella1 Just checking in — were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!