Add a new revision when a published document changes. Earlier signatures stay linked to the version each person signed.
Who can do this: owners and administrators.
Publish the updated version
- Open Documents and select the document.
- Open Revisions and click New Draft. If a draft already exists, continue working on it.
- Add the new content using the editor, an upload, or a cloud import. For a document based on an uploaded file, prepare the updated file and upload or import it into the draft.
- Optionally fill in What changed. This note is for your team’s revision history; it is not shown to people receiving the document.
- Wait for saving or file processing to finish. To get feedback, request review. Turn on Require approval before publishing if approval is required.
- Click Publish when the draft is ready. If approval is required, every reviewer must approve the latest content first.
While you edit a new draft, Workspace shows Unpublished changes. The current published version remains available until you publish the update. Use Finish draft to continue editing.
The new revision becomes current. Previous published revisions and completed records remain available.
Ask people to sign the update
Publishing alone does not email people or cancel old requests.
For a document with Requires a signature on:
- Open Compliance after publishing.
- Review the people who need the current version. Earlier completions may show Outdated.
- Select a person to open the Document compliance side panel.
- Use Send request in that side panel to send the updated version.
To choose several people, open the three-dot menu on the document’s Workspace or Compliance tab and choose Send request. Select the people in To, check the selected Document, preview the email, and send. See send to one or more people.
The Send requests button at the top of the page does not resend to people with Outdated completions. It is for missing requests.
You can also use a group’s Send missing for eligible missing requests.
When you send a new request for the same person and document, pending requests for older revisions are canceled. Completed, expired, and previously canceled requests stay in history.
What if someone still has the old link?
Before you send a replacement request, the old pending request continues to refer to its original revision. Completing it records a signature for that version, not the new one.
After it is canceled by a replacement request, the old request cannot be completed. Ask the person to use the new email or their signing portal.
Update a document available to read
When Requires a signature is off, publishing a revision changes the file people can open through their groups. There is no signature request, availability email, or record of opening the document.
See make documents available to read.
Repeat signatures without changing the document
You do not need a new revision for a recurring sign-off. Use renewal to ask people to sign the same published document again on a schedule. Last modified on November 3, 2026
