Set it up in an afternoon, not a quarter.

Most fleets are running DocVigia in under an hour without help from us: a guided wizard builds the workspace, a spreadsheet brings in the fleet and its documents, and the QR stickers print from the platform. This page is the map of that, and of the API underneath it.

Start here

Three steps, in this order.

The wizard opens by itself the first time somebody signs in, and it walks the same three steps. Nothing below needs an implementation call.

01

Build the workspace

Company, sites, and the catalogs: document types, unit types, trip types and the requirement matrix that says which documents each combination must carry. Mexico is preloaded and every row is editable.

02

Bring in the fleet

One spreadsheet carries the units, the drivers and their documents. Scans and photographs go through AI/OCR, which reads the expiry dates rather than asking somebody to type them. A SharePoint library can be imported on a schedule instead.

03

Put a phone on the gate

Print the QR stickers from the platform, stick one on each unit, and open the guard screen on any phone. The scan returns GO or NO-GO and writes the gate log — no hardware, and it works with the signal a yard actually has.

Roles

Who sees what, and who gets told.

Roles are configurable — the list below is the set DocVigia ships with, and the permission matrix behind it is editable per company. Alerts follow the same map: an expiring policy reaches finance, a licence reaches HR.

Role What it opens on
Administrator Everything: catalogs, roles, alert recipients, billing
Fleet / dispatch Units, coupling readiness, what may leave today
Guard The scan screen and the gate log, nothing else
Driver Their own documents, uploaded from a phone
HR Licences and medical certificates, not policies
Legal Renewals in flight and the audit trail
Finance Policies, fines and what the fines cost
API

A REST API, included in every plan.

JSON over HTTPS, secured with a JWT. Send Authorization: Bearer <token> on every request; everything you read is scoped to the authenticated company, without a tenant parameter you could get wrong.

Endpoint What it does
POST /api/v1/auth/login Obtain an access token
GET /api/v1/units List units, paginated
GET /api/v1/documents List documents in the vault, with expiry dates
GET /api/v1/gate/scans Gate events and their GO / NO-GO verdicts
GET /api/v1/alerts What expires next, and who was told
GET /api/v1.1/sync/{entity} Mobile contract — fleet sync for the driver app

The written guides are still being written

Step-by-step walkthroughs per role, the full endpoint reference and the webhook catalog are in progress, and this page will carry them as they land. Until then, the product itself is the guide — the wizard, the import and the gate screen all explain themselves — and anything they do not, [email protected] will.