Start with an approved source
Connect a supported source and confirm the people who should have access. Brain does not turn a restricted source into a public one.
For workspace administrators
Give your team AI access with rules you can inspect
As more people and agents use company knowledge, an administrator needs to see who can reach what. Brain applies source permissions and agent scope on retrieval and records access in a content-blind audit trail.
For workspace owners, it, and security teams. Signup availability and current limits are shown before purchase.
The workflow
From question to evidence
Scope an agent
Create a distinct agent identity and give it only the access needed for its task. You can revoke access when its work ends.
Verify allowed and denied retrieval
Ask about both approved and restricted material. Inspect citations and the access record to check what was reached or withheld.
What to check
Verify the experience yourself
People and agents have identities
The same governed brain can serve both, with separate access decisions for each requester.
Access is recorded without content
The audit trail records the access decision and can be independently checked without copying the underlying document into the log.
Start at your size
Organization plans are priced per seat; the pricing page gives current limits and billing terms before checkout.
Questions, answered
Does every agent inherit its creator’s access?
No. Agents use scoped credentials and can be restricted independently. Test the exact scope before production use.
Which sources are available now?
Google Drive and Notion are available as connected sources. Check the in-app connector catalog for the current options and your plan’s limits.
Can we verify the audit record ourselves?
Brain provides a tamper-evident, content-blind record that can be independently checked. The public demo shows the workflow; validate it with your own workspace before relying on it.