Brain · Use cases
New hires get answers with sources from their first morning, without asking the same five people.
Monday: how do I book leave?
The fictional handbook directs employees to submit a request in the leave system and wait for their manager’s confirmation. The example does not submit a request or decide whether leave is approved.
Source excerpt · Employee handbookSubmit your leave request in the leave system. Your manager confirms approval.
A new hire’s first week is a stream of practical questions: where to request leave, how to ask for access, who owns a process and what a team means by a particular term. The answers may exist, but finding the right document can require asking the same colleague several times.
A connected onboarding collection makes those documents easier to consult. Brain’s role is to help a new hire locate an answer and inspect its source. It should support the relationship with an onboarding buddy, and it should leave personal, sensitive or ambiguous questions with the responsible human.
The first week also exposes gaps between a checklist and the guidance behind it. A new hire may have completed an introduction without knowing where to request design-file access or who reviews a customer announcement. Keep those procedures in an owned handbook or team guide, with the responsible person named when the question needs a decision.
Use five ordinary questions to review your onboarding collection before inviting the next starter. Check the answer against its source, try the limited-access example, and give the new hire a clear route to their buddy or people team. Update the original guidance when a process changes so the next person can consult the same maintained reference.
Connect. Ask. Govern.
Choose the approved starter checklist, role guide and policy collection. Name the owners and review dates so a new teammate can distinguish current onboarding steps from an old process someone remembers.
Ask where to find the first-week guidance or how to route a practical request. Inspect the cited instruction before acting, and keep the manager or policy owner available for exceptions the reference does not resolve.
Give the new hire the collection appropriate to the role. Test a restricted personnel source separately and review access when the person’s responsibilities change rather than granting the entire company archive on arrival.
See the idea in action
Fictional examples. These interactions do not query your Brain or test real permissions.
The fictional handbook directs employees to submit a request in the leave system and wait for their manager’s confirmation. The example does not submit a request or decide whether leave is approved.
Submit your leave request in the leave system. Your manager confirms approval.
The fictional access guide says to request the project folder through the help desk, include the project name and identify the approving owner. It gives the new hire a route to ask for access without exposing documents they cannot view.
Request project-folder access through the help desk, with the project name and approving owner.
The fictional communications checklist names the product lead for accuracy and the marketing lead for tone. The new hire can read the checklist before drafting, then ask the actual owners to resolve exceptions.
Product lead: factual review. Marketing lead: voice and publication review.
The fictional week-one checklist asks for a short introduction, a list of current tasks and one question about the team’s process. It makes preparation visible without expecting the new hire to reconstruct an old meeting thread.
Bring your introduction, current tasks and one process question.
The fictional compensation material is restricted to the people team. A limited-access teammate sees a withheld notice instead of the answer and source excerpt. The correct next step is a conversation with the people team, not another prompt intended to bypass access.
Restricted example: compensation planning is owned by the people team.
Open a question, then inspect its source excerpts.
A new teammate can ask a compatible Claude, Cursor or Codex client about leave, file access or review responsibilities through MCP. Brain connects that question to the approved onboarding sources, with citations to inspect. The assistant does not submit leave, approve access or replace the manager and onboarding buddy.
Start with the approved handbook, role-specific access instructions and week-one checklist. Drive and Notion can supply maintained guidance, while approved uploaded documents cover a focused reference set. Keep restricted compensation planning outside the general onboarding collection.
Point leave and benefits questions to the relevant maintained section, with the source’s existing access intact.
Keep access-request steps, communications reviewers and the first-week checklist with their responsible owners.
Add approved orientation documents for the role. Review private employee material separately before adding it.
Keep access intentional
Starter guidance, benefits references and private employee records have different audiences. Keep the onboarding collection intentionally scoped and test a new teammate’s actual membership. Sources explain the established process; they do not approve a personnel decision, change an employment term or replace the responsible manager’s judgment.
Connected-source permissions apply to onboarding answers. A teammate who cannot open a compensation document in the source cannot obtain its contents by asking Brain a different question.
Every question is tied to a named person or agent. A dedicated agent key has a scope distinct from its owner’s permissions, keeping a starter-guidance assistant separate from people-team planning.
The content-blind audit records the requester, the sources reached or withheld, and when the access happened. It records the access decision without copying handbook passages or private employee details into that record.
Brain’s own models are not trained on connected onboarding material. Managed model processing uses terms that prohibit training on the permitted excerpts sent for an answer. If your team supplies a model key, its agreement with that provider governs the request; see the privacy policy.
Fictional metadata only. No document content is shown, and this is not a record from your account or proof of live enforcement.
A first-week question may need one checklist item and its exception rather than every HR chapter. Compare a focused answer with the complete-reference baseline and retain the context needed for correctness. Evaluate model input, retrieval, outputs and Brain charges together when assessing the onboarding workflow.
Compare current plans and limits| Approach | What to consider |
|---|---|
| An onboarding buddy | Provides personal context, encouragement and judgment. Repeated factual questions can take time away from that relationship. |
| Checklist software | Tracks tasks and completion. A completed task does not necessarily mean the new hire understands the underlying guidance. |
| A wiki and Brain | Keeps guidance in owned documents and gives people a way to ask about it. The documents still need current owners and appropriate access. |
AI can help new hires find routine information, understand unfamiliar terms and locate the document behind an answer. Begin with a maintained handbook and a small collection of common questions. Human support remains essential for personal circumstances, interpretation and decisions. Review answers before treating the workflow as part of your onboarding process.
Start with practical questions about leave requests, access procedures, meeting preparation and who owns a process. Prefer questions whose answers are recorded in an approved document. Avoid using the assistant to infer private employee information or make employment decisions. A useful response explains the procedure and points to the current source.
Assign owners to the handbook and team guides, and correct the original documents when procedures change. Check the connector’s actual update behavior rather than assuming instant synchronization. Periodically repeat your common onboarding questions and inspect the citations. A dated source or conflicting answer should trigger a review by the responsible team.
Workspace and source access should reflect what a new hire needs for their role. Verify those boundaries with a separate test identity before importing sensitive material. The limited-access cards on this page are fictional illustrations and do not prove live enforcement. Questions about compensation or personal employee records belong with the authorized people team.
Setup depends on your source collection, connector availability, workspace settings and review process. Start with a few approved documents and a handful of common questions so you can inspect the answers before expanding. There is no universal setup-time promise here; the important milestone is a useful, current answer with an appropriate source.
An onboarding buddy helps someone understand the team, build relationships and navigate uncertainty. A connected knowledge layer can support that person by handling repeated document-based questions. Keep a clear route to a human whenever the answer is missing, contradictory or personal. Good onboarding combines useful information with the judgment and care of colleagues.
Start with your handbook and five questions new hires ask most often. Keep a human owner available when the documents are not enough.
Employee handbook
Access guide