Somebody on your team answers the same five questions about the same long document every week. The answers are in the document. Nobody reads two hundred pages to find one paragraph, so they ask a person instead.
Docutrain deletes that step. Upload the document, let it train, share the link. Anyone who opens it asks a question in ordinary language and gets an answer assembled from your content, with numbered citations pointing back at the passages it came from. No code to write, no model to choose, no prompt to compose.
It is defined by what it refuses
The constraint is the product. An assistant answers from the documents it was trained on: not the open internet, not the model's own general knowledge, and not a plausible-sounding blend of the two.
Ask about something the document does not cover and you get a refusal under a heading reading Not in this document, instead of a confident paragraph you would then have to go and check.
That is a smaller promise than a general-purpose chatbot makes. It is also a far more verifiable one, and verifiability is the entire reason to put a document behind a chat box rather than a search field. How a grounded answer is built walks through the machinery, including the source viewer that shows you the original passage and its page number.
Three kinds of people, three different products
Askers are the end users, meaning anyone chatting with a trained assistant. They arrive through a shared link, a widget on somebody's website, an organization's own domain, or Slack and Telegram. For public documents they need no account at all, and most of them never see a dashboard in their lives. This is the majority of everyone who will ever touch your assistant.
Owner admins are on the other side of the glass, uploading documents, branding the experience, managing members and deciding who can open what. The group's first administrator, the primary admin, also holds billing.
Super admins are Docutrain's own platform operators, with sections ordinary customers never see. Where this series mentions something super-admin-only, it says so.
There is a fourth position worth naming, because it is easy to forget it exists: the registered user who belongs to an owner group but administers nothing. They sign in, browse and chat with whatever their groups have shared with them, and can request access to further groups from their profile. They have no Home section, so signing in drops them straight into Documents, which is exactly right for someone whose job is to read rather than to configure. Roles are covered properly in users, roles and invitations.
Five words that carry the product
A document is anything trained: an uploaded file, pasted text, an audio recording, a scraped web page. An owner group is the organization that holds documents, branding, members and a plan, also called a workspace, and perfectly happy being a group of one. A collection is a curated set of documents behind a single link, optionally passcode-protected. Chat is where questions go in and cited answers come out. And your plan, which is Free, Pro, Business, or the Enterprise tier whose badge reads Unlimited, sets the limits laid out in plans and limits.
Those five words appear in every screen and every post in this series. They are the whole vocabulary.
What you can train it on
PDFs, Word files, PowerPoint, Excel and Markdown, as you would expect. Text you paste in directly. Audio, so lectures, meetings and podcasts, transcribed automatically on the plans that include it. A public web page, scraped, where that is enabled.
And forms, which is the one people miss. You can build a form, collect responses, and then make the accumulated responses chattable, turning a pile of submissions into something you can interrogate instead of a spreadsheet nobody opens. See forms that become knowledge.
Sizes, page limits and the per-format details are in training your first assistant.
Readers arrive sideways
Almost nobody reaches your assistant through Docutrain's front door. They arrive through something you handed them: a direct link to one document, a link to your whole library, a collection link with a passcode, a shared conversation someone forwarded, an embedded widget inside a page they were already reading, a Slack or Telegram bot, or your own domain, where the whole experience carries your branding and never mentions ours.
Which of those routes works for a given reader comes down to one setting: the document's access level, which is Public, Passcode, Token link, Registered, Owner group, or Owner admins only. Every one of those is checked on Docutrain's servers on every request, so none of it can be talked around in a browser. The trade-offs, including the fact that public and passcode sharing are paid features, are in access levels explained.
You do not need an account to chat with a public document. You need one to open restricted documents shared with you, and to build assistants of your own. Starting a group is free.
The honest summary
If you are evaluating Docutrain: it is good at making a fixed body of material answerable and checkable, and it is deliberately bad at answering anything else.
Whether that reads as a limitation or as the entire point depends on what you were planning to use it for.