Documents

Document management with versions, owners, and permissions

Document management is how a company knows which file is current, who may read it, and how it is found later. We build that library for contracts, policies, drawings, and case files, and we make it safe to put an assistant on top.

Library and types
Versions
Permissions
Retrieval

Talk To Sales Contact

A shared drive is not a system

Folders named “final final” do not have versions, owners, or a retention rule. The product we build has a document type, a status, an access rule, and a history. Search has to work for a person in a hurry, which means titles and metadata, not only the full text.

The AI dependency

A retrieval assistant is only as safe as this library. If permissions are wrong here, they will be wrong in the assistant. The RAG page assumes a corpus with an owner. This is that corpus.

The current file is obvious

The first library

One current version
Who may read and replace it
A history of the change

Not a dump

Every shared drive on day one
A search that ignores permission
Legal conclusions about retention

What changes document software

The type

Contracts, drawings, and procedures have different owners and different “current” rules.

The secret

A file the wrong branch can open is a failed release.

The end

Say what happens to a replaced file. Leaving both visible is how people use the old one.

What a document brief needs

01
The type
Contracts, drawings, or procedures. One library first.
02
Current
How you know which file is the one.
03
The secret
Who must not open it.
04
The end
What happens to a file you replace.

Marks the current file is the one people open

01
A file has an owner
Someone is responsible for the document, not only for the folder.
02
Version is explicit
The copy people open is the current one, and the older one is still there.
03
Access follows the role
A person sees the files their job allows.
04
Search finds current
A search result is the live file, not an export from last year with the same title.

What we build

Library and types

Contracts, policies, drawings, or case files, each with the fields they need.

Versions

A current file, a history, and a note of what changed.

Permissions

Department, matter, or project rules enforced on download, not only on the menu.

Retrieval

Search for people, and a permission-aware source for an assistant.

Questions we hear

Can you import our existing drive?

Yes, as a project with rules for what is in scope. Importing every duplicate and personal file is how the new system starts dirty.

Does this replace SharePoint?

Not by default. If SharePoint is the library, we may build the workflow and the assistant beside it. A replacement needs a reason stronger than preference.

How long do you keep documents?

You set retention with your advisers. The system must be able to apply it, including deletion, rather than keep everything forever by accident.

A shared drive is not a system

The AI dependency

The current file is obvious