jump to content

Document management

See how platform documents move through version projects, approval quorums, electronic signatures, publication, archiving and PDF export.

Show as Markdown

Platform documents are controlled records for policies, procedures, reports and other compliance materials.A document has a life cycle; its versions retain the content and decisions that were current at a time.

stateDiagram-v2
  state "Draft version" as draft
  state "Approval quorum" as review
  state "Published version" as published
  state "Signature requested" as signing

  [*] --> draft: Create a version
  draft --> review: Request approval
  review --> draft: Rejected
  review --> published: Approved and published
  draft --> published: Publish
  published --> signing: Request signatures
  signing --> published: Signed, cancelled, or voided
  published --> [*]: Superseded by a new version
The lifecycle of a single version of the document. Archiving applies to the document, not a single version.

Edit the work in a project version. Publishing creates the version for use or review. Archived documents remain part of the record, but are removed from active use. Avoid editing a document just to change its approval history; create a new version when controlled content changes.

A approval quorum defines who must decide before a document can continue. Decisions are recorded against a specific version so that subsequent revisions do not rewrite the history of a previous approval.

Signature requests also belong to a version of the document. A request can be completed, cancelled or cancelled depending on its status.

Documents can be exported as PDFs and linked to controls and measures. A controlled document explains what the organization intends to do; evidence demonstrates that a measure has worked.

Access to projects, approvals and signatures follows organization authorization. Use the audit log when investigating changes to controlled records. Roles and permissions.

Ultima actualizare: