Document repository
Where the organization's policies live, with a review workflow and a controlled path to the Trust Center.
What lives here
The repository holds the documents an organization must be able to produce: policies, procedures, plans. It is where the things an auditor asks for live — and where a published continuity plan lands, because ISO 22301 requires documented information and a plan that exists only on a screen does not satisfy that.
Draft, review, published
Each document moves through three states. Draft is work in progress. In review is the state where somebody other than the author has to look. Published is the version in force.
The workflow exists because an unreviewed policy is the most common way a document ends up asserting something the organization no longer does.
Starting from a template
Documents can be created from templates rather than from a blank page. And the editor accepts images, because a procedure with a diagram is easier to follow than a procedure in prose.
Translation is part of the flow too: a document can be translated into the platform's other languages without becoming a second document with a life of its own.
Publishing here is not publishing out there
Publishing in the repository makes the document the version in force internally. It does not go to the Trust Center because of that.
Exposing a document publicly is a second, separate, deliberate act. The separation is a safety line: no internal approval flow should be able to publish a document to the internet as a side effect, when nobody decided to make it public.