This is where account admins will establish defaults for the general proof settings.

They are divided into 3 categories:

Proofing defaults

  1. Minor version - this feature allows proofs to be labeled as v0.1, v0.2, v0.3, etc. for internal review cycles.

  2. Lock the proof when all decisions are made - this option will auto-lock the proof when all decisions are made.

  3. Allow download of the original file - this allows reviewers to download the proof file without any comments or

  4. Suppress proof created/failed email - this prevents the proof creator from receiving the initial email that goes out letting them know that they have a new proof to review.

  5. Proof security - this allows you to select who the proof should be shared with and whether or not they need to authenticate themselves when opening the proof. This functionality ensures that only designated reviewers can access proofs. You can read more about it here.

Proof sharing

  1. Require guest reviewers to authenticate - if you decide that guest reviewers need to authenticate themselves before they can access the proof, you can determine how often they need to be authenticated.

  2. Allow sharing proofs with - this allows you to choose who the proofs can be shared with: anyone, users in my account, or users in my trusted accounts.

Folder sharing

  1. Folder shareable link - enables the possibility of sharing folders with generated URLs. Read more about this feature in this article.

Other settings

  1. Make folders mandatory - by selecting this option, proof creators will be required to choose which older the proof should be placed in before they can complete the proof creation process.

  2. Allow historical workflow deadlines - gives users the option to set a deadline in the past.

  3. On the new version set the proof name to the first file's name - instead of requiring new versions to take on the previous version name, we've added an administrator setting that allows users to select if a new version should be named after the previous version or the first file’s name.

  4. Deadlines: relative based on the previous version - setting allows deadlines to be copied relative to that previous version’s creation date. If the first stage had 2 days between the deadline date and the creation date, when creating a new version of the proof, the deadline would be 2 days from that time. The automatic deadline recalculation is based on business days and does not include Saturdays and Sundays.

  5. Download expiration date - decide how will it take for a download original file link to expire.

  6. Show custom properties for - decide to whom custom proof properties should be displayed.

  7. Allow reviewers to view previous versions - if this box is checked, reviewers will have visibility to all versions of proof, regardless of what stage they are in.

  8. Allow reviewers to mention all contact in the account - allow reviewers to share permissions on a proof to @mention anyone from the account contact list.

  9. Allow reviewers to @mention reviewers in other stages - you can determine whether or not reviewers will be able to @mention people in other stages.

  10. View full workflow (Enterprise Edition only) - switch this setting if you want to keep the full workflow visibility for all users and guests. By default, users and guest reviewers can only see those parts of the workflow that they are shared with.

Did this answer your question?