Your documentation, kept, organised, and answerable.
DocuDriver holds your organization's analytics and technical documentation, turns it into a curated data dictionary, and answers questions from it. Only from it, and only for the people allowed to see it.
Access is by invitation from your organization. There is no public sign-up.
How it works
Upload what you have: models, reports, SQL, packages, and the documents around them. The product reads the structure, proposes the dictionary, and answers from it with the source named every time.
Upload the deliverables
Power BI files and models, SQL, SSRS reports, SSIS packages, dbt projects, notebooks, Office documents, and code. Extraction keeps structure and metadata only: table names, fields, measures, queries, lineage. Never a data row.
Approve the dictionary
Every table, field, measure, and query is proposed as a draft with its definition and source. Your people approve, edit, or reject. The product never invents a definition and never publishes one nobody approved.
Ask, and get a cited answer
The assistant retrieves only from documents the member is allowed to ask, cites what it used, and says so when the answer is not in the documentation. Access rules are enforced at the database, not in the prompt.
with movers as step).Retention you can defend
Review, archive, and version rules per collection, legal holds that freeze everything under them, and a purge window with a restore queue. Nothing is ever silently deleted.
A dictionary that proposes, and people approve
Definitions come from the delivered files themselves and carry their source. One dictionary per collection, retired when it empties, exportable for anyone who needs it on paper.
An assistant that cites or declines
Answers come only from documents the member may ask, with the source named every time. When the documentation does not say, the assistant says that instead.
Built for the whole organization
One workspace for the whole organization, isolated at the database, with your own name, colours, and logo. Every department, team, and office is a group inside it: roles, collection grants, and a hierarchy decide who can see, ask, or download each source, so the finance team sees finance's documentation, the registrar's people see the registrar's, and nobody sees anyone else's. A part of the organization that needs a sealed space of its own gets an additional workspace. A college, a hospital group, an insurer, a logistics firm: the same product, with your name on it.
Security
The controls are in the database and the platform, not in the prompt, so they hold whatever a question says.
Isolation per workspace
Every table carries the workspace, and Postgres row-level security filters every query. A member of one workspace cannot reach another's, even through the assistant.
Sign-in protection
Two-factor authentication, required per workspace if the owner chooses; sign-in throttling and a full sign-in trail; a list of active sessions with sign out anywhere; an inactivity timeout.
Metadata only
Extraction keeps table names, fields, measures, queries, and lineage. Customer, employee, and student records are never read, stored, or sent to a model.
Audit trail and retention
Every upload, approval, grant, hold, and setting change is logged with who and when. Nothing is deleted silently, and a legal hold freezes everything under it.