Document Management

The Documentation section is the central, versioned library for an audit. It holds every policy, procedure, report and certificate, and lets you link documents to assessments as evidence, download any version, roll back to an earlier one, or set the version everyone should reference.

The document library

Each row represents a document and shows its name, how many versions exist, which version is the active reference, when it was last updated, the requirements it supports and who uploaded the latest version.

Uploading and versioning

Upload a file of any type and it appears in the library, ready to link as evidence. Every time you upload a new file for an existing document, Governy keeps it as a new version and preserves the full history.

• Set the active version — choose which version approvers see; the choice applies everywhere that document is used as evidence.
• Roll back — make an earlier version the active one again.
• Download — grab the active version, or any specific version from the history panel.

Linking to evidence

From any assessment, choose Link existing document, browse the library and attach the document. One document can support many requirements at the same time.

Activity log

Every document keeps a log of who uploaded each version, when, and which version is currently the reference.

Secure storage

Documents are kept in secure storage. The page shows the connection status: when connected, all upload and download actions are available; if it’s temporarily unavailable, previously stored documents remain accessible. See ESIA Connectors for more on integrations.

Who can do what

Action	Admin	Domain Manager	Analyst	Approver	Auditee	Reader
View library	✓	✓	✓	✓	✓	✓
Upload document / version	✓	✓	✓	✗	✓	✗
Set active version	✓	✓	✓	✗	✓	✗
Roll back version	✓	✓	✓	✗	✗	✗
Download any version	✓	✓	✓	✓	✓	✓
Delete document	✓	✓	✓	✗	✗	✗

Best practices

• Name documents clearly — include the control reference or document type.
• Set the reference version after review — only once the right owner has approved it.
• Keep the history — old versions are valuable evidence for certification.
• Link broadly — one policy can support every requirement it covers.