An ops team of four supports about ninety people. The employee handbook is a 60-page PDF last opened by someone other than its author in March. There are eleven policy documents in a folder, an expenses guide, and three onboarding decks presented live every quarter.
New starters read none of it. They ask their manager, who asks ops, who answers the same carry-over holiday question for the fourth time this month.
That is a retrieval problem rather than a content problem. Here is the order to do the setup in.
Decide who can open it before you upload anything
Onboarding material is internal, so the access level you want is Owner group: signed-in members of your organization can open it, and nobody else can, link or no link. Set it per document, or set it once on the upload queue's defaults strip so a whole batch lands correctly.
Two neighbors are worth knowing. Owner admins only narrows a document to administrators, which is the right home for a policy still in draft. Registered means any signed-in Docutrain user, which is far broader than your company and almost never what an HR team wants. See access levels explained.
Sort out seats before you invite ninety people
Then bring people in, and here is the thing that catches teams out.
Your plan's member allowance counts current members plus unexpired pending invitations. Send ninety invitations and you have consumed ninety seats, whether or not anyone has accepted. Hit the cap and the invite flow blocks with an upgrade prompt, and the same check runs when you approve a join request.
Single-seat plans exist. A team intending to onboard ninety people should settle its tier first, not discover the ceiling on invitation number six.
Invitations are otherwise the smoothest route in, because an invited user skips both the approval queue and email verification. Links last 30 days, pending ones sit in the Users list with an expiry warning, and resending cancels the old link. If the address already belongs to a Docutrain account there is no signup at all: they are added immediately.
One rule to plan around: only the primary admin, your group's first administrator, can invite someone as an owner admin. Ordinary admins invite members. See users, roles and invitations.
Getting the material in
The handbook and policy PDFs go up in one queued batch. They are prose with the occasional figure, so answer Document when Docutrain asks what type of PDF it is.
The onboarding decks need a different decision, and the upload screen tells you plainly. Docutrain accepts .pptx, but a direct PowerPoint upload extracts text only, so the slides themselves never appear in chat. Export the deck to PDF and choose Slide deck instead, and Docutrain captures every page whole so the assistant can present an entire slide inside an answer.
For a benefits deck with a table that is far easier to look at than to describe, that is the difference between a useful answer and a paragraph attempting to narrate a grid. Google Slides works the same way.
What a new starter meets in the first thirty seconds
Two settings do most of the work here.
The intro message is the formatted welcome in the chat sidebar. The detail worth exploiting: if it contains a list of sample questions, readers can click any of them to ask it immediately. Write the four questions every new hire actually has and your welcome text becomes a working menu rather than decoration. Docutrain will draft a starting point from the document's own content if you ask it to.
The composer prompt is a small card above the chat input, shown before the first message. You choose whether readers can dismiss it, whether it disappears once chatting begins, and how long a dismissal sticks.
Use it to say what the assistant does not cover. "Policies and the handbook, not payroll queries" sets an expectation before somebody is disappointed by a refusal, and it costs one sentence.
If your team lives in Slack, the assistant can go there too. Channels are paired with documents, and asking in the channel means the answer appears in the channel, so the next four people with the same question read it instead of asking. For group-restricted documents the bot checks the asker's email against Docutrain's records before answering. Setup is arranged with the Docutrain team.
Checking that any of it landed
Reading a policy and understanding it are different things, and the gap is exactly where compliance training usually fails.
The Quiz tab generates a bank from the document, sized to its length, with an explanation and page citations on every question. Answers are graded on the server, so the key never reaches the reader's browser.
Read the bank before showing it to anyone. Each question expands to show its options with the correct one marked, and editing one creates a new version while retiring the old, so a starter's completed attempt still shows the wording they were actually asked. That property is what makes quiz results worth keeping as a record.
Generating questions does not show them to anyone. A separate toggle puts the Quiz button in the chat, and it stays disabled until a bank exists.
The statistic to watch is the average score. A low average on material your team knows well says more about the policy's wording than about the people reading it. See quizzes.
When the policy changes
Replace all data suits a new edition of the handbook. The previous content keeps answering questions the whole time the new content processes, and the switchover happens in one step, so the assistant never goes dark on ninety people mid-afternoon.
Add to existing data appends, which is right for a new appendix, and it can be undone from the history. Replace cannot.
Three follow-ups after a substantial retrain. The abstract is flagged stale and wants regenerating. Quiz questions are not regenerated automatically, since they were written from the old content, so review them. And leave a note on the training row: "v4 handbook, new parental leave section" reads considerably better in eight months than a bare timestamp. See retraining and history.
The cheapest content roadmap you will get
Read the conversations. The feed shows every question asked, with a red dot on answers a reader marked unhelpful and the reason they picked.
Those red dots are your handbook's to-do list. A recurring question with a consistently poor answer almost always means a paragraph is missing, and now you know which paragraph, and how many people wanted it.