Use caseProcurement

Find documents in plain words

Lucy needs a signed contract and its notice period by Thursday. It was filed years ago under a supplier name that has since changed.

A question in plain words finds the documentEvery answer names the documents it usedAccess rights apply before the search runs

The assistant4 documents found

Your payroll provider is Paylink Inc., called Arbor Payroll until 2023. The signed data processing agreement is dated March 4, 2021.

source · supplier contracts, 4 documents
What the search returns

The document answers · it opens at the cited page

Questions to the repository
01

What gets in the way

In a nutshell

Arbor Payroll became Paylink Inc. in 2023, and nobody renamed the folder. That is how documents go missing in a repository: filed under a supplier's old name, a project that ended, a folder created by someone who left. Staff search by file name, then ask around. IT gets asked to open broad access to speed things up, and compliance refuses. The search ends with a colleague's memory.

Lucy types her question the way she would ask a colleague. The assistant turns it into a search on content and metadata, with her rights, and returns the documents it used. Each person finds everything their access allows, and nothing more.

Ask the repositoryWorkspace
One sentence, four documents. Lucy's question in, a table out, each row naming its document class.
Search sourcesAI console
Oliver's side of the search. One task in the console, with its model and where it runs.

A search box and a settings page look like nothing new. The care is in the order: rights are set where the documents live, the question is asked in plain words, the answer names its documents, and every exchange is kept. The steps below start with Oliver's access settings and end with his November usage counts.

02

What the search may read

Before anyone searches, Oliver settles two things: who may read what, and where the model runs.

Step 1Repository

Rights stay where the documents live

Oliver Mercer is IT director at a company of 2,400 people. In the repository, access is set by group, down to the document. Procurement reads supplier contracts. Legal owns a litigation space that only its own group opens. The search adds no rights of its own.

Repository · AccessRepository
The assistant reads with the rights of the person asking. Permissions apply before the call.
Search never widens accessA wrong right is fixed where the document lives. Oliver does not run a second set of permissions for the AI.
Step 2AI console

The model runs on the company's servers

Contracts hold prices, names and personal data. Oliver sets the search task on a model hosted at the company's site, and the data residency routing rule keeps every call there. Usage is tracked by department, so he can tell who uses the search.

Task settings · Search the repositoryAI console
The model is chosen per task and can change without a redeploy.
The documents stay where they areNothing is copied into a new space with looser rights, and no contract leaves the company's network to be searched.
03

A question in her own words

Lucy meets the payroll provider on Thursday about the renewal, and needs the signed agreement and the notice period.

Step 3Assistant

A document she cannot name

Lucy Gardner does not remember the provider's former name or where the agreement was filed. She types: the signed data processing agreement with our payroll provider. The question becomes a search, and the answer comes back as a table of four documents, each naming its document class.

Ask the repositoryWorkspace
A click on a row opens the document.
Try it on your own repository: how many documents can only be found by the person who filed them?
The document is found by what it saysThe former supplier name is in the documents themselves. Lucy did not have to know it, or know who filed the contract.
Step 4Viewer

The notice period, read in the contract

Lucy opens the services agreement in the viewer and asks how much notice the company must give to leave. The answer quotes clause 14.2 and its page. She reads the clause herself before writing the date in her notes.

Payroll services agreement.pdfViewer
The answer points to the page it comes from, so the reader checks it in one click.
The answer comes with its clauseLucy walks into the meeting with the exact wording, at its page, and works out the date herself.
Step 5Viewer

What the amendment changed

The table listed an amendment from 2025. Lucy asks what it changed compared with the agreement. The answer names the clause it touched: exhibit 3, the list of sub-processors, with two names added. Every other clause stays as signed in 2021.

Compare · Agreement and amendment 1Viewer
Additions, deletions and changes show on one screen.
Two documents are read as oneLucy knows which clauses the amendment moved without reading both contracts end to end.
Step 6Assistant

A question her rights do not cover

Lucy asks whether there has ever been a dispute with Paylink. The answer comes only from documents she may open, and none mentions one. She emails Helen Faber in legal, who asks the same question with her own rights. Helen finds a 2025 settlement and tells Lucy what she can use for Thursday.

Ask the repositoryAI console
Two people, the same question, two answers: each one built from what that person may read.
The owner of the content decides what is sharedHelen reads the settlement and chooses what Lucy needs. The litigation space stays closed to procurement.
04

Keeping search accountable

Lucy has what she needs. The results go into her renewal file, and IT reads how the search is used.

Step 7Workspace

The result table goes into the renewal file

Lucy exports the table of documents to Excel for her renewal file. Each row keeps the document name, its class and its status, so her manager finds the same documents with his own access.

Paylink renewalWorkspace
The export lists the documents. Whoever opens one in the repository does so with their own rights.
The answer can be passed onThe file her manager opens lists the documents. Lucy does not attach copies to an email.
Step 8AI console

The IT director reads the exchanges

Every Monday Oliver opens the exchanges in the console. Each one keeps the user, the question, the answer, the cited documents, the model and the date. He sees that facilities staff often search for the same lease documents, and asks them to agree on a document class.

Exchanges · Search the repositoryAI console
Every exchange is kept per user, with provider, model, date and cited source.
Security gets a record it can readWho asked what, which documents answered and which model ran, kept for every exchange.
Step 9Reporting

Usage is counted by department

The console counts requests and tokens by department. Procurement and facilities use the search most. Oliver brings the counts to the steering committee instead of a guess about adoption.

Statistics · Search the repositoryAI console
Consumption is tracked by use and by department.
Adoption is measured from real useOliver knows which teams rely on the search and what it costs them, department by department.
05

The possible results

Lucy's questions about Paylink hit all three cases in one morning. Each case gives the person asking a different next move.

Found

The document answers

The table names the document and its class, and the answer quotes the page.

Next: the reader opens it and checks the clause herself.
Several versions

A draft and a signed copy

The table lists both, with their status, so nobody quotes the draft by mistake.

Next: the reader picks the signed copy, or compares the two in the viewer.
Nothing in your rights

No readable document answers

The answer says so, and comes only from documents the person may open.

Next: the question goes to the team that owns the subject, which searches with its own rights.
What the AI leaves to you

It grants no access. It shows nothing the person asking could not open. Across the nine steps on this page, access is decided by the people who own the content, where it is stored.

The assistant turns a sentence into a search and quotes its sources. Permissions apply before the call, and every exchange is kept with its model and date.

06

What it saves

Counted on Lucy's search before the Paylink renewal. A repository with tighter document classes would return shorter tables.

1 sentenceto find the signed agreement, without the file name or the supplier's former name.
4 documentscited in the answer, each one a click away.
0 rightswidened for the search. Legal kept its space closed and answered itself.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

Three principles behind the figures

Found by meaningProductivityA question in plain words reaches documents filed under names nobody remembers.
Rights before the callSecurityEach search runs with the rights of the person asking. Nothing is copied to a looser space.
Sources on every answerA person decidesAnswers name their documents and pages. The reader checks and chooses what to use.
07

Who it helps

The people who search, the people who run the repository and the people who guard access all have a stake, and each applies its own test.

End users

Procurement, facilities, any team that files

The document exists, and only the person who filed it knows where.

  • Ask in your own words, without a file name.
  • Results come as a table, with each document's class.
  • Answers quote the page they come from.
  • Export the results to Excel for your own file.
IT and architecture

CIOs and architects

Each search tool you have tried wanted its own copy of the documents and its own rights.

  • The search reads the repository with the user's rights.
  • The model is chosen per task and can run on site.
  • Every exchange keeps its question, answer, sources, model and date.
  • Usage is counted by department.
Risk and compliance

Legal and compliance

Someone always wants broad access opened so people find things faster.

  • Restricted spaces stay restricted.
  • The AI grants no access and reveals no hidden document.
  • Each answer names the documents it used.
  • Contracts can stay on the company's own servers.

A good first step

Open the plain-language search on one document class first, such as the supplier contracts your teams ask about most. A few weeks of real questions will show what people actually look for.

Your repository, your document classes and your access rights stay as they are.

Next step

See it on your own repository

Bring a few questions your teams ask every week and a test set of anonymized documents. We will run the search with two users who have different rights, and compare.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.