Try Pro free for 14 daysHeyBrain is now live for general availability; join leading teams using HeyBrain!Start Free

PLATFORM · SECURITY

Secure AI for business that proves what it accessed

Secure AI for business starts with access boundaries. Scope people and agents to company knowledge, then review their access records.

  • Permissions you already have.
  • Ask from Claude, Cursor or Codex.
  • Keep private knowledge private.

See the clearance. Follow the access record.

Sources for Permissions you already have

Permissions you already have

Authorized roleAllowed

The contractor can read the project brief.

Outside scopeWithheld

The finance folder is outside the contractor's assigned access.

Permissions you already have1
Sources for A record of every access

A record of every access

Question to source wording
Recorded requester, sources and time

The access record shows the named user, source identifiers and request time.1

Access decision review

Open the referenced policy to review the access decision.1

Open the cited wording before using it

A record of every access1

Built for IT, Security, Compliance, Leadership

Can a contractor see the finance folder?

The contractor can read the project brief. The finance folder is outside the contractor's assigned access. 1

Permissions you already have

Say yes to AI. Keep the receipts.

Your IT and security share answers with sources.

  • IT

    Permissions you already have

    • Can a contractor see the finance folder?

      On request

    • Which project sources can the contractor read?

      Before deciding

    Source answer: The contractor can read the project brief. The finance folder is outside the contractor's assigned access.

    Sources: Permissions you already have (Google Drive); Fern Works · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • Security

    Every agent gets its own key

    • Which agents can read HR?

      Weekly

    • Which HR handbook can the assistant use without payroll access?

      Before deciding

    Source answer: The HR assistant has access to the policy handbook. Payroll records are outside its key's scope.

    Sources: Every agent gets its own key (Notion); Fern Works · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • Compliance

    A record of every access

    • Who asked about the Fern Works contract this week?

      On request

    • What identity, time and source references appear in the access record?

      Before deciding

    Source answer: The access record shows the named user, source identifiers and request time. Open the referenced policy to review the access decision.

    Recorded requester, sources and time
    The access record shows the named user, source identifiers and request time.
    Access decision review
    Open the referenced policy to review the access decision.

    Sources: A record of every access (Google Drive); Fern Works · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • Leadership

    Review model provider terms

    • Which data-use terms apply to our model connection?

      Weekly

    • Which provider terms govern this model connection’s data use and retention?

      Before deciding

    Source answer: The workspace uses your selected model connection. Review that provider’s data-use and retention terms alongside your organization’s agreement.

    Sources: Review model provider terms (Notion); Fern Works · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • IT

    Bring your own model key

    • Which model connection does this workspace use?

      On request

    • How do the agent’s identity and scope apply when we use our own model key?

      Before deciding

    Source answer: The workspace uses your model key. Agent permissions remain tied to each agent's own identity and scope.

    • Model connection: your provider
    • Knowledge scope: your workspace

    Sources: Bring your own model key (Google Drive); Fern Works · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • Security

    Review privacy controls

    • Where are our processing and privacy terms?

      Weekly

    • Where can our reviewer find the processing terms and privacy contact?

      Before deciding

    Source answer: The published privacy policy describes data handling, providers and international transfers. Contact the privacy address for the contractual documents your organization needs.

    Sources: Review privacy controls (Notion); Fern Works · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive

Less searching. More shared context.

Without HeyBrain

With HeyBrain

Check the contractor’s project and finance access in separate records.

Find the project brief the contractor can read while the finance folder remains outside their assigned access.

Look up the HR assistant’s permitted sources and key scope separately.

Find the policy handbook the assistant can use while payroll records remain outside its key’s scope.

Assemble the requester, source references and time before reviewing an access decision.

Find the named user, source identifiers and request time, then open the referenced policy to review the decision.

Locate the selected model connection and collect its provider terms for review.

Find the workspace’s selected model connection and review the provider’s data-use and retention terms alongside your organization’s agreement.

ONE CONNECTED BRAIN

One question, across your tools

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

Question
Can a contractor see the finance folder?
Answer
The contractor can read the project brief. The finance folder is outside the contractor's assigned access. (Source 1)
  • Source 1: Permissions you already have (Google Drive)
  • Additional source: Every agent gets its own key (Notion)
  • Additional source: A record of every access (Google Drive)

FOLLOW THE SOURCE

Review the evidence behind an answer

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

Answer
The HR assistant has access to the policy handbook. Payroll records are outside its key's scope. (Source 1)
Cited excerpt from Every agent gets its own key (Notion)
The HR assistant has access to the policy handbook. Payroll records are outside its key's scope.
  • Source 1: Every agent gets its own key (Notion)
  • Source 2: Permissions you already have (Google Drive)

PERMISSIONS IN EVERY ANSWER

Share the context. Keep the boundaries.

Same question, different permissions. Review the request and sources in the access record.

Question
What does the incident review record?
Answer for Rafael Vale (Security lead)
Response procedure and actions available. Finding: shared access needs review.
Answer for Jonas Okafor (Department lead)
Response procedure and actions available. Restricted section withheld.
Section withheld from Jonas Okafor
INCIDENT FINDINGS · SECURITY ONLY
Access record
14:02 · Jonas Okafor · Source access checked · 1 SECTION WITHHELD · RECORDED

Company knowledge, under your control

Permissions you already have

Answers respect source access.

Every agent gets its own key

Set its scope. Revoke its key.

A record of every access

Review requesters, sources and access decisions.

Review provider data terms

Check provider data use and retention.

Bring your own model key

Connect your model to governed knowledge.

LESS CONTEXT. LOWER COST.

Send less context per task

HeyBrain sends only the context a task needs.

Repeated contextWhole documents
With HeyBrainRelevant passages

FAQ

Questions teams ask

  • Can a contractor see the finance folder?

    The contractor can read the project brief. The finance folder is outside the contractor's assigned access. 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 agents can read HR?

    The HR assistant has access to the policy handbook. Payroll records are outside its key's scope. 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 agent has its own key and scope. Administrators review requesters, times and source references in activity records alongside workspace membership and source 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 individual agent scopes with each team’s responsibilities.

  • How does HeyBrain reduce AI token cost?

    HeyBrain sends only the context a task needs instead of repeatedly passing whole documents to your AI tool. Use the context calculator to compare the amount you send and your input price. 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