4.1. Central Repository

In most organizations, contracts are not lost — they are just not easy to find. They are in a SharePoint folder, but no one knows exactly which one. Or on a colleague's laptop, who happens to be on leave. Or in an email thread, attached somewhere during a negotiation. Or printed out, sitting in a filing cabinet that was last opened five years ago.

📁
A SharePoint folder — but no one knows exactly which one
💻
A colleague's laptop — who happens to be on leave
📧
An email attachment — buried in a negotiation thread
🗄️
A filing cabinet — last opened five years ago

If locating the relevant documents takes days, that is not an archiving problem — it is an operational vulnerability.

One Source, Full Control

Fluenta One manages every contract-related document in a single, centrally governed repository. The document does not live on an individual's machine; it belongs to the organization. This straightforward shift fundamentally changes the risk profile.

The system handles all document types:

PDF Word file Excel attachment Email archive Scanned paper (OCR)
  • Full version control — every previous iteration is retained, and the audit log records who changed what and when
  • Finalized contracts are locked — they cannot be accidentally deleted or overwritten
  • OCR capability — scanned paper-based documents can be digitized and made searchable within the same system

Role-Based Access Control

Centralized storage does not mean everyone sees everything. Fluenta One applies role-based and attribute-based access control (RBAC/ABAC), with permissions configured according to organizational roles:

Role Scope Permission
HR Employment contracts only Edit
Procurement team Supplier contracts only Edit
CFO All contracts Read only
Legal team All contracts Edit

This ensures that sensitive data — payment terms, strategic discounts, confidential side conditions — does not reach unauthorized parties, while everyone retains access to what they need to do their job, without having to raise an IT ticket.

The System as Institutional Memory

One of the less obvious values of a central repository is institutional memory. When a colleague leaves the organization, the contractual knowledge does not leave with them, because it was never stored only in their head. When a negotiation requires a precedent from five years ago, it is retrievable in seconds, not after hours of searching.

A qualitative difference

Compared to shared folder structures, this is not an incremental improvement — it is a qualitative one. A transparent, secure, searchable system is not just more convenient; it enables a structurally different level of control.