Document Management

(DMS)

One place for the files the business actually runs on: supplier invoices, signed contracts, delivery notes, certificates and product assets. Every file is attached to the record it belongs to, versioned and permission-controlled.

Attachments Versioning Permissions Full-Text Search Retention Audit Trail

Key Features

One place for the files the business actually runs on: supplier invoices, signed contracts, delivery notes, certificates and product assets.

Attached to the Record

A document belongs to an order, a supplier, an employee or a product, not to a shared folder someone has to go find.

Versioning

Every upload keeps the previous version. See who replaced what and when, and restore an earlier version if needed.

Permissions

Visibility follows the same roles as the rest of the platform. A document is only as visible as the record it hangs off.

Full-Text Search

Search inside documents, not just filenames. Find the contract clause or the invoice number without opening files one by one.

Retention Policies

Retention rules per document type, with automatic expiry and legal hold when a record must not be deleted.

Audit Trail

Who uploaded, viewed, downloaded or deleted a file, with timestamps. Exportable for audits.

Kubrik OS — agent layer

Document Management, assisted and operated by AI

Documents are where the AI's reading ability turns into posted transactions instead of a filing cabinet.

AI-assisted

What the AI advises on

Available on every plan, Starter included.

Reads supplier invoices, delivery notes and contracts and extracts the fields that matter
Finds the document behind a transaction, and the transaction behind a document
Flags documents approaching a retention, renewal or expiry date

AI-operated

What the AI does under governance

Professional and Enterprise. Starter runs the AI in advisory mode only.

Files incoming documents against the record they belong to, with the extracted data attached
Creates supplier invoice drafts from received documents and routes them for approval
Applies retention policies and version control on schedule

Governed tools an agent can call in this module

extractDocumentData() attachToRecord() createInvoiceDraft() applyRetentionPolicy()

Autonomy is a setting, not a promise — choose the rung per role and per module

Suggest

The agent proposes. Nothing changes until a person acts on it.

Prepare

The agent builds the transaction and leaves it waiting for approval.

Execute below threshold

Acts on its own under a value or risk limit you set.

Execute by policy

Acts inside a written policy, every action fully audited.

Escalate

Anything outside the policy stops and goes to a person.

Same rules, either operator. An agent obeys the same permissions, validation and business rules a person does, and every action lands in the audit trail: who or what initiated it, the inputs, the rationale, the approvals, the resulting transaction and how to reverse it.