> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gumloop.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Personal vs Team vs Organization Brain

Every knowledge source has a **scope** that decides who can see and search it, and each scope has its own rules for who can add and manage sources.

| Scope            | Who can see and search it                                                 | Who can add and manage sources       |
| ---------------- | ------------------------------------------------------------------------- | ------------------------------------ |
| **Personal**     | Only you                                                                  | Anyone, for their own personal Brain |
| **Team**         | Members of that team                                                      | Team admins                          |
| **Organization** | Everyone in the organization, or only the teams the source is shared with | Organization admins and managers     |

## Personal Brain

Your private space, at **Personal > Brain**. Sources you add here are visible only to you, and every member can add their own. Agents you attach a personal source to can use it only in your own chats.

## Team Brain

Lives on each team's page. Sources here are visible to all members of that team, so one teammate can index a shared Drive folder or Slack channel once for the whole team. Adding and managing team sources requires a **team admin** role on that team (this applies to organization admins too). Regular team members can search but not add.

## Organization Brain

Managed at **Settings > Organization > Brain**. Sources here can be shared with the entire organization or restricted to specific teams, chosen when the source is added. Adding and managing them requires an organization **admin** or **manager** role. This is where company wide knowledge (policies, handbooks, the shared Drive) usually lives, set up once for everyone.

<Note>Whatever the scope, you must be a member of the owning organization to see a source. Being added to a team without joining its organization is not enough. Custom roles can also restrict Brain access or source management further.</Note>

## FAQ

<AccordionGroup>
  <Accordion title="I want my whole team to search a folder I indexed personally">
    Personal sources stay personal. Add the source to the team's Brain instead (or ask a team admin to), or ask an admin to add it at the organization level.
  </Accordion>

  <Accordion title="I am a team member and cannot add a source to the team">
    Adding team sources requires a team admin role on that team. Ask one of the team's admins.
  </Accordion>

  <Accordion title="Can an organization source be hidden from some teams?">
    Yes. When adding an organization source you can share it with everyone or restrict it to specific teams.
  </Accordion>

  <Accordion title="Does scope decide who sees every document in the source?">
    Scope is the first gate. Sources with Document access set to Original source additionally check each document's own permissions in the original system. See [Why is a document missing from Brain?](/help/brain/why-is-a-document-missing)
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Why can't I see a knowledge source?" icon="eye-slash" href="/help/brain/why-cant-i-see-a-knowledge-source">
    Org and team membership checks
  </Card>

  <Card title="Brain" icon="brain" href="/core-concepts/brain">
    Full feature reference
  </Card>
</CardGroup>