Manage proof access to avoid second stages

[spencer_w]

Hi all, 

Searching the forum saw some chatter on this topic, but I wasn't able to find a concrete solution. 

Currently, some of our users are wandering into projects and opening proofs without having been added as reviewers. 

This automatically generates a second stage of review with no deadline, which throws a wrench into our reporting and dashboards. 

Is there a global setting we can enable to prevent this behavior? Or generate a "request access" screen if a user tries to open a proof they weren't added to? 

Advice is much appreciated! 

[KellieNYL]

Basically, the users are inheriting access to the documents through object-level permissions, which gives them access to open the proof as well.

Try playing with object-level permissions or locking down inherited access to documents through the access level. 

[spencer_w]

Thanks! I tested a modified access level that removed the "automatically inherit document permissions." 

This prevented the user from seeing any documents in the project, which is good for our 'curious' folks. 

However, when the user was added to a task, they also did not inherit document permissions -- which is a problem. Task owners need to be able to see the project documents.

Also, when the test user was added to the proof for review the document was not automatically shared with them. 

I take this to mean we'd have to add them to the proof and manually share the document with them to allow them access? 

If so, that's unfortunately not tenable for our workflow due to high user volume per proof.