# Structure of DevHub

> How organizations, projects, MCP folders and vaults fit together, and what each one inherits.

DevHub arranges your work in a tree.

```text
Organization
├── Organization vault      (knowledge of the whole organization)
└── Project                 (one repository you work on)
    ├── Repository vault    (technical knowledge of this repository)
    └── MCP folder          (the folder on disk that agents may open)
```

## Each level

- **Organization.** A business or ownership context. It holds projects and one organization vault.
- **Project.** One repository. It belongs to an organization, has a repository vault and one or more MCP folders.
- **MCP folder.** A folder on your disk. It belongs to a project, and an agent working in it reads nothing without one. DevHub builds an index of its code, the Repository Index.
- **Vault.** A folder of Markdown notes. An organization vault is inherited by all projects of the organization.

## What is shared

The library, which holds skills, commands, personas, rules and instructions, is shared by every organization. [Business Context](/devhub/features/business-context/index.md) never mixes the notes of two organizations in one answer, so a scope always names one organization or one project.

## What you can switch off

A folder or a vault can be disabled, or a vault set to read-only, without deleting anything. Removing an entry in DevHub does not delete the folder or the notes on disk.

## Related

- [Organizations and projects](/devhub/features/organizations-projects/index.md)
- [Vaults](/devhub/features/vaults/index.md)
- [How DevHub works](/devhub/concepts/how-devhub-works/index.md)