Try Pro free for 14 days (card required)HeyBrain is now generally available.Start Free

USE CASES · EMPLOYEE ONBOARDING

AI for employee onboarding, with answers from day one

Use AI for employee onboarding to answer new hires’ questions from team knowledge. Keep the policy or guide beside each answer.

  • Book leave.
  • Ask from Claude, Cursor or Codex.
  • Keep private knowledge private.

Built for HR, People ops, Team leads, New hires

How do I book leave?

The leave handbook links to the request form and identifies your manager as the approval owner. 1

Book leaveExample

Week one, without the shoulder taps.

Your HR and people ops share answers with sources.

  • HRExample

    Book leave

    • How do I book leave?

      On request

    • Which leave form should I use, and who approves it?

      Before deciding

    Source answer: The leave handbook links to the request form and identifies your manager as the approval owner.

    Leave handbook
    Find the request process
    Request form
    Linked from the handbook
    Approval owner
    Your manager

    Sources: Book leave (Google Drive); Quarry Works · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • People opsExample

    Get the right tools

    • Which tools do I need access to?

      Weekly

    • Who grants access to each tool on my team checklist?

      Before deciding

    Source answer: The team checklist names the tools you need and the person responsible for granting access.

    Tools you need
    Named in the team checklist
    Access owner
    The person responsible for granting access

    Sources: Get the right tools (Notion); Quarry Works · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • Team leadsExample

    Understand releases

    • How does our release process work?

      On request

    • Which checks must be complete before the team lead’s release decision?

      Before deciding

    Source answer: The release runbook lists review, testing and deployment checks. The team lead owns the final release decision.

    Review
    Open the runbook’s review checks
    Testing
    Read the testing checks
    Deployment
    The team lead owns the final release decision

    Sources: Understand releases (Google Drive); Quarry Works · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • New hiresExample

    Find the decision owner

    • Who owns pricing decisions?

      Weekly

    • Which pricing decisions need both product and finance review?

      Before deciding

    Source answer: The pricing decision log names the product lead and finance reviewer. The current plan sheet contains the latest amounts.

    Product lead
    Named in the pricing decision log
    Finance reviewer
    Named in the same decision log
    Latest amounts
    Read the current plan sheet

    Sources: Find the decision owner (Notion); Quarry Works · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • HRExample

    Check expenses

    • What is the travel expense limit?

      On request

    • Which travel expenses require approval before I submit the form?

      Before deciding

    Source answer: The travel policy sets the expense categories and approval steps. The linked form records your request.

    Expense categories
    Set out in the travel policy
    Approval steps
    Follow the linked policy
    Request record
    Complete the linked form in its own tool

    Sources: Check expenses (Google Drive); Quarry Works · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • People opsExample

    Keep salary bands private

    • Who can read salary bands?

      Weekly

    • Which handbook guidance is available without HR salary-band access?

      Before deciding

    Source answer: The employee handbook is available. Salary bands are restricted to the HR team.

    Employee
    Employee handbook
    HR only
    Salary bands

    Sources: Keep salary bands private (Notion); Quarry Works · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive

Less searching. More shared context.

Without HeyBrain

With HeyBrain

Ask a colleague where to request leave and who approves it.

Find the request form in the leave handbook and identify your manager as the approval owner.

Ask teammates which tools you need and who grants access.

Ask the team checklist for the required tools and their access owners.

Search the runbook for release checks and the final decision owner.

Find review, testing and deployment checks, with the team lead owning the final release decision.

Check handbook access separately from HR salary-band permissions.

Read the employee handbook while salary bands remain restricted to HR.

ONE CONNECTED BRAIN

One question, across your tools

Bring Google Drive, Notion and your uploads into one cited answer.

Question
How do I book leave?
Answer
The leave handbook links to the request form and identifies your manager as the approval owner. (Source 1)
  • Source 1: Book leave (Google Drive)
  • Additional source: Get the right tools (Notion)
  • Additional source: Understand releases (Google Drive)

Illustrative example, fictional data

FOLLOW THE SOURCE

Review the evidence behind an answer

Open the citation. Read the original wording and surrounding detail.

Answer
The team checklist names the tools you need and the person responsible for granting access. (Source 1)
Cited excerpt from Get the right tools (Notion)
The team checklist names the tools you need and the person responsible for granting access.
  • Source 1: Get the right tools (Notion)
  • Source 2: Book leave (Google Drive)

Illustrative example, fictional data

PERMISSIONS IN EVERY ANSWER

Share the context. Keep the boundaries.

Same question, different permissions. Review the request in the activity record.

Question
What should I read in my first week?
Answer for Zara Vale (HR lead)
Induction checklist and leave policy available. Band B: $55,000–$65,000.
Answer for Tomas Okafor (New hire)
Induction checklist and leave policy available. The restricted source is not in your access.
Not in Tomas Okafor’s access
SALARY BANDS · HR ONLY
Access record
14:02 · Tomas Okafor · Asked the brain · RECORDED

Illustrative example, fictional data

Company knowledge, under your control

Source sharing, where we can prove it

Google Drive, GitHub and Slack (beta) sharing carries into HeyBrain. Notion uses the connecting account’s access.

Every AI tool gets its own key

It acts with your access. Revoke it any time.

An activity record

Review questions asked, uploads, syncs and blocked or masked data.

Review provider data terms

Check provider data use and retention.

Bring your own model key

Connect your model to governed knowledge.

SEND PASSAGES, NOT WHOLE FILES

Send less context per task

HeyBrain sends relevant passages instead of whole documents.

Repeated contextWhole documents
With HeyBrainRelevant passages

FAQ

Questions employee onboarding ask

  • How do I book leave?

    The leave handbook links to the request form and identifies your manager as the approval owner. Ask follow-ups in the same conversation and open each citation to check the surrounding detail, then share the source with colleagues who can access the same collection.

  • Which tools do I need access to?

    The team checklist names the tools you need and the person responsible for granting access. Connect the relevant Drive folder or Notion pages, or upload documents, then follow citations to their original passages from the AI tools your colleagues already use.

  • Which sources and AI tools can we use?

    Connect Google Drive, Notion and document uploads; Claude, Cursor and Codex ask your company knowledge through HeyBrain MCP. Keep decisions and references available where your team works. HeyBrain supplies knowledge; agents use their own tools for actions requested by the user.

  • How does HeyBrain keep private knowledge private?

    People and agents receive answers from sources they can open. Workspace rules restrict the audience; each AI tool has its own revocable key that acts with its member’s access. Administrators review who asked and when in the activity record, alongside workspace membership and access rules.

  • How do we get the team started?

    Connect your team’s current brief, decision notes and working guide, invite the people who need them and ask a familiar question. Open its source citations before expanding the collection. Align workspace membership and each governed agent’s policy with each team’s responsibilities.

  • How does HeyBrain reduce AI token cost?

    HeyBrain sends relevant passages instead of whole documents to your AI tool. Compare costs with the context calculator on the Reduce AI token costs page. Your team shares the same connected knowledge across tools, so every new conversation can start with the relevant passages and their sources.

/ Get started today

Put your company knowledge
to work with HeyBrain