Publishing or moving proofs from private sections

Question

Accepted Answer

Publishing proofs from private sections.
When working with proofs in private sections, you have several options for publishing or moving them to other sections. This guide explains the different publishing options and when to use them.
Publishing Options
Publish as a New proof
Creates a fresh proof in the target section
Starts a new review process
No previous comments are carried over
Perfect for sharing finalized work with clients
When to use:
Starting fresh client reviews
Creating clean versions for external sharing
Separating internal and external feedback
Moving from internal drafts to client-ready versions
Publish as a New version
Updates an existing proof in the target section
Maintains the current review process
Preserves version history
Ideal for iterative reviews
When to use:
Updating existing client reviews
Maintaining version history
Continuing ongoing discussions
Making minor updates to existing proofs
New to Sections? Learn more about Public Section & Private Sections
How to Publish
Step 1
To publish a proof, hover over the proof and click on the proof and head to publish as per the image below.

Step 2
Publishing as a new proof
Under the Destination column, select New Proof, give your proof a name and click on the publish button

Publishing as a new version
Under the Destination column, select New Version, Select or search for the proof you want to publish to. Click the publish button

Key Things to Know
Comments and Feedback
Comments stay in the original private section
New versions start with a clean comment thread
Previous versions remain accessible in the original section
Version Control
Original proof remains in the private section
Published versions can be traced back
Each section maintains its own version history
Access Control
Only members with access to private sections can publish
Published proofs inherit the target section's visibility
External reviewers only see proofs in regular sections
Best Practices
When Publishing for Client Review
Ensure all internal reviews are complete
Remove any sensitive internal comments
Publish as a New proof for a clean start
Use clear version naming conventions
When Publishing for Team Review
Consider whether to maintain version history
Choose appropriate target sections
Inform team members of new publications
Use consistent publishing workflows
Version Management
Keep original versions in private sections
Use descriptive version names
Archive old versions when needed
Maintain clear publishing trails
Common Scenarios
Scenario 1: Initial Client Review
Complete internal reviews
Publish as New proof to client section
Start fresh client feedback process
Scenario 2: Iterative Updates
Make requested changes
Publish as New version
Continue existing review process
Scenario 3: Multiple Stakeholders
Use private sections for initial reviews
Publish to different sections for different stakeholders
Maintain separate feedback streams