Governance

Review changes and retain publication evidence

Follow an update from Author submission to Publisher review, signature, and release, with a durable record of the decision.

8 min read
Digilnk Publisher inbox showing a submitted update, per-change approval, and signed publication controls.
Publisher inbox with a fictional submitted update. This is the current change-review interface.

Confirm responsibilities

An administrator assigns Author and Publisher responsibilities and activates simpler change reviews in a governed workspace. Workspace access and content responsibilities are separate.

  1. Ensure the people preparing changes have Author responsibility and suitable workspace access.
  2. Assign at least one eligible Publisher to review and release updates.
  3. Use People and responsibilities to confirm assignments before submitting.

Submit the complete update

Authors save product or company content before opening Review & submit changes. The review captures a fixed snapshot of the proposed release.

  1. Inspect the saved changes and discard any items that should not be included.
  2. Enter a summary explaining the purpose of the update.
  3. For a product announcement, confirm the exact subject and summary that subscribers should receive.
  4. Submit the update. The system assigns an eligible Publisher; My reviews shows assigned work.
Digilnk saved-draft comparison drawer with Review changes and Submit update steps.
Review & submit changes: compare the saved draft before submitting it to a Publisher. Select the image to view it full size.

Review, correct, and publish

The assigned Publisher reviews the update from the Publisher inbox. Approvals apply to the submitted content, not to future edits.

  1. Approve changes individually or use Approve all changes after checking the entire update.
  2. Discuss corrections on the relevant change. Resolve requested corrections individually.
  3. Use Return for changes when the Author needs to edit. Resubmission creates a fresh review and resets approvals.
  4. When all changes are approved, choose Sign and publish complete update and complete authentication.

Retrieve the evidence

Use the governance and compliance tools available to your role to inspect review history, signatures, and publication records. Publication packages retain content hashes, and inspection exports include the associated evidence.

  1. Review the submission’s decisions and discussions when investigating a release.
  2. Use publication-package verification to check recorded integrity.
  3. Have an administrator or appropriately authorized compliance user generate an inspection export or manage retention and quality holds.
Next guide

Manage product update subscriptions

Continue →