Templates, generated documents, extraction schemas โ organized, versioned, governed, searched. One Library. Zero shadow drives.
DocIQ Library is the shared knowledge store underneath the suite. Every document Create publishes lands here. Every result Extract saves lives here. Every template Create uses, every schema Extract runs โ versioned, permissioned, audit-trailed, and findable in two seconds.
"The hardest part of any document program is finding the current authoritative version. We made that the default โ not the exception."
Every regulated organization has the same horror story. The auditor asks for the policy as it stood in March. Three SharePoint sites are searched. Four people email screenshots. Two say "I think this was the version." Nobody is sure. The lawyers get nervous.
DocIQ Library makes that story impossible. Every document, template, and schema has a stable ID. Every change creates a new version. Every prior version is archived, not deleted, with a forward pointer to what superseded it. The "what was true on March 14" question has exactly one answer.
And it's the same store every other DocIQ module reads from. One Library. Five jobs. No shadow copies.
One thing Library is not Library is the index, not the storage. Your bytes stay in S3, SharePoint, Box, OneDrive, Drive โ wherever they already live. Library stores the IDs, the versions, the metadata, the audit log, and the workflow state. Migration is not a precondition for governance.
Protected. Always present. Maintained by the platform. Add any number of custom collections on top โ but these three are the foundation every DocIQ workflow assumes.
The five system templates plus every custom template your tenant creates. Versioned. Brand-kit aware. Fork to customize. The library Create reads from on every generation.
Every document Create publishes lands here automatically. Stable DOC-YYYY-NNNNN IDs. Approval state on the badge. Supersession chain preserved. The single source of truth for every generated artifact.
The four system schemas plus every custom schema your tenant defines. Versioned. Field-typed. The library Extract picks from on every batch. Re-runs against historical batches stay reproducible.
System collections are fixed. Custom collections are yours. Nest folders as deep as you need. Move items across collections. Pin what matters. Search the whole tree from one place.
โ K from anywhere. The result list mixes documents, templates, and schemas โ relevance-ranked, not collection-segregated. Match terms get highlighted. Click an item, jump to it. Find what you need before you've finished typing.
When a new version supersedes an old one, the old version is archived โ not deleted. The chain is preserved. Auditors get the full timeline. Operators get one clear current version.
Every SOP Create publishes lands in Library. Versioned. Pinned by the operations team. Found by Chat when an examiner asks a question. No more "which version is current?" emails.
Pension operationsAudit packets live here. Evidence rows from Extract land here. Auditors get one URL, one search bar, full chain of custody. The audit week stops being a fire drill.
GRC / auditDefine an extraction schema once. Use it across every batch. Version it when fields change. Re-run historical batches against the new version. Reproducibility, governed centrally.
Data operationsBrand templates, regulated-doc templates, departmental conventions โ all live in Templates collection. Forked when needed; system originals never touched. One source for the look and feel.
Document programBring a real document mess โ multiple versions, scattered across drives, with the "current" one ambiguous. We'll show you what it looks like inside Library: indexed, versioned, governed, found in two seconds.