Set Up Onboarding

Set Up Onboarding

Build one onboarding space, add an assistant that answers from it, and read the questions it could not answer. Each unanswered question tells you which page to write next. This is a loop, not a chat window: the new hire asks, the assistant answers with a source or admits it cannot, the gap is recorded, an admin closes it.

What goes in the space

Part	In Folio
Materials	Ordinary pages: welcome, a 30/60/90 plan, the product in one page, the process, prices, a glossary. Start from the onboarding checklist template (CC0)
Week-one check	A data table with a form on top: the newcomer answers on Friday, the manager reads the rows (Data Tables and Forms)
Process board	A whiteboard with the main process drawn out (Boards)
Assistant rules	Pages in the space's .agent folder: how to answer, tone, escalation. Only space administrators see them
Gaps	Questions without an answer in Assistant analytics

Steps

1. Create the space and add the pages. A _templates folder in the space can hold your own starting pages.
2. Add the form. Create the table "Week-one check answers" with the questions as columns and add a form. Test it with a spare account before sending it.
3. Write the .agent rules. Add pages such as How to answer (short answers, a Sources: line with links), Tone and Escalation (when to send the person to a human). Starter pages are in the repository's onboarding package.
4. Invite the newcomer as an editor, or a viewer if they only read. The assistant reads only what that person could open.
5. Turn on the assistant: connect a Cursor key, personal or shared (Set Up Folio AI). The newcomer opens the panel in Ask mode.
6. Read the gaps weekly. As an admin, open Assistant analytics, tab Questions without an answer: the person's own words, what was missing and the pages the assistant read. Write the missing page; the next person who asks gets the answer with its source.

Space administrators see analytics for the spaces they administer; instance administrators see all. Opening a conversation is written to the audit log and shown to everyone on that conversation.

Signals you get

• 👍 / 👎 on each saved answer.
• A survey after every third answer: Yes, Partly, No or Not now.
• A report from the assistant itself when the pages do not hold the answer or it had to infer one.

Without the built-in assistant

An external agent can answer from the same pages with a read token of the newcomer's own user (Connect AI Agents). It does not record unanswered questions, and .agent pages are not visible to it, so put the rules on an ordinary page and tell the client to read it first.

Limits

• Needs a Cursor key; the pages the assistant reads go to Cursor.
• Search is keyword-based. A miss can mean a missing page or a missed search.
• Answer links are written by the model; the check is the click.
• The list holds what was flagged, rated down or caught by the survey; a confident wrong answer nobody rates is not on it.
• Fixing is manual: analytics do not edit pages.
• The public demo has the assistant off; the setup is a description plus starter pages, not a one-click template.

See also

Blog: new hires ask the wiki · Onboarding checklist template · Video: onboarding a sales rep · Video: Folio AI analytics