1. Documentor
  2. Deployment scenarios
Fictional organisations · full setup · day-to-day operation

What Documentor could look like for you.

Four fictional organisations that show how archives, groups, roles and sorting fit together. The companies, people and numbers are invented – just like the ZOO Plyšákov sample archive in the application screenshots.

Scenario 1 · manufacturer, 180 people

Kovolis engineering works: standards, drawings and service in one place.

Standards sit on a shared drive, drawings come as PDFs from the design office, service manuals are in the foremen’s drawers and material certificates reach the quality department by e-mail. The design engineer looks for a requirement in a standard, the technician for a tightening torque, quality for the certificate for a batch.

  • Setup
  • Deploymentyour data, our operations: files in S3 storage in the company’s server room, we run the application and index
  • ArchivesStandards and regulations, Drawings and processes, Service and manuals, Quality
  • GroupsEngineering, Production and service, Quality; the head of quality is the group administrator of Quality
  • Roleseveryone is a Reader of Standards; Engineering are Processors in Drawings, service in Service, and quality is Archive administrator of Quality; IT is Supervisor
  • External AIallowed in Standards and Service; Drawings and Quality do not allow it – text there is read by OCR and searched, and AI there uses only models on the company’s own server
  • Intakethe inbox Supplier documentation with an e-mail mailbox: certificates to Quality, manuals to Service by similarity; the quality technician sorts the e-mail
  • Codescertificates carry the batch number in a Data Matrix; in Quality, the rule ^SARZE- → label certificate, and search by batch number
  • In operation
  • Design engineer“What surface roughness does our directive prescribe for sealing faces?” – an answer citing the clause of the directive and the standard it refers to
  • Technicianlooks up tightening torques at the machine; the result shows the manual’s table with the row highlighted
  • Qualityconfirms the suggestions from e-mail in the morning with one click, and sees in the daily digest how many are waiting to be filed
  • ITan e-mail about a processing error when a document cannot be processed (a damaged PDF, say); in Usage, tokens by archive
  1. Week 1

    Archives and groups

    Four archives, three user groups, sign-in with the company’s Microsoft accounts.

  2. Week 2

    Import

    Standards and manuals in batches into the archive folders, processing overnight; checking errors in the queue.

  3. Week 3

    Instructions and labels

    Instructions for the AI in each archive, code reading and the batch rule in Quality.

  4. Week 4

    Intake

    The supplier inbox with manual confirmation; after a month, a decision based on Agreement of suggestions.

Scenario 2 · a town’s building management

Town of Lipová Hora: sixty buildings, thirty years of inspections.

The technical department manages schools, sports facilities and municipal buildings. The building records from the nineties are on paper, and external inspection technicians supply the inspection reports. Documents must not leave the town’s infrastructure.

  • Setup
  • Deploymententirely on premises: in the town’s data centre, updates done remotely by Advisor software
  • ArchivesBuilding records, Inspections and checks, Projects and construction
  • GroupsTechnical department (Processor in all of them), Inspection technicians with Google accounts (Processor only in Inspections), Management (Reader)
  • AI modelsonly models on the town’s server, in the DEFAULT group; no archive allows an external model
  • StorageS3 in the town’s data centre, the group’s default storage
  • Scansold building records in batches from the filing office; for scans with an unreadable layer from the scanner, Documentor’s own OCR
  • In operation
  • Inspection technicianuploads the report into the Inspections archive themselves; cannot see the other archives
  • Clerkthe research “which buildings have an unremedied defect in their electrical inspection” – it goes through the archive document by document
  • Head of departmenta daily digest of new documents by e-mail at 7:00
  • Auditeveryone sees on their profile where each of their roles comes from; the Supervisor blocks a technician’s account when the contract ends
Scenario 3 · design studio, 25 people

Atelier Mostník: an archive for every job.

Every larger job has its own documentation and its own external partners – the structural engineer, the client, the general contractor. The drawing management system sends finished PDFs on its own, and partners sign in with their own accounts.

  • Setup
  • Deploymententirely with us: the studio has no servers of its own, just a browser
  • Archivesone per job (Job 2026-014 Na Výsluní apartment building…) and a shared Standards and templates
  • Roleslead designers are Archive creators: they create the archive for a new job themselves and are its administrators
  • Partnersthe structural engineer and the client with accounts from other organisations, Readers of their own job’s archive only
  • Intakethe drawing system sends through the API with the code of the job’s archive; the suggestion is chosen by the sender and automation is on
  • Labelslanguage model: technical report, drawing, bill of quantities, site meeting minutes
  • In operation
  • Designer“Does the floor build-up differ between the technical report and the drawing?” – both places, each with a citation
  • Clientsearches in their own job; sees neither the other jobs nor the studio’s standards
  • New jobthe lead designer creates the archive and adds the partners, the Supervisor adds it to the inbox targets and the drawing system starts sending
  • End of the jobthe partners’ roles are removed, the archive stays searchable for the studio
Scenario 4 · a group of three companies

Severka Group: one installation, three companies, each kept separate.

Logistics, building materials and service share IT and accounting, but each company’s data must stay separate and AI costs have to be recharged. Invoices arrive in one mailbox and from the scanner in the filing office.

  • Setup
  • Deploymententirely on premises: in the group IT’s cluster, each company with its own S3 storage
  • Groupsone per company; in each, a group administrator from the company’s management
  • Configurationeach group has its own S3 storage; service may use an external model, logistics and building materials only models on the group’s server
  • Changesgroup administrators propose a new connection, IT as Supervisor tests the connection and approves it
  • Invoice intakethe inbox Received invoices (e-mail and the scanner folder) with the targets Invoices – Logistics, – Building materials, – Service
  • Code rulesQR Platba (the Czech QR payment code) to a given company’s account (ACC:CZ…) → that company’s archive; invoices without a QR code by similarity
  • Automationon: scans from the filing office are filed by rule on their own, e-mails are always confirmed by the accountant
  • In operation
  • Accountantsees the code rule label in triage, confirms the e-mails and looks up an invoice by its payment reference
  • Group administratoradds a new colleague to their company’s group; sees the usage of their own people only
  • ITexports usage by group to Excel every month for recharging; moves a company’s archive to new storage while it stays in use
And one more

ZOO Plyšákov: the archive we show it on.

A zoo for plush animals with a decree, standards, operating rules, breeding sheets, a scan from 1987 and invoices for hollow fibre stuffing. All the application screenshots on this website come from it – no real customer documents.

Screenshots →

Documents of the ZOO Plyšákov archive: the Upload documents panel with the supported formats and a list of 35 documents with a first-page thumbnail, name and main heading, page count, processing state and upload date
Documents of the ZOO Plyšákov archiveSample

We will show you how it works on your own documents.

Send us a few PDFs from your archive – old scans are fine. In 30 minutes you will see how searching them works and how the chat answers.

Already a customer? Sign in