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

# Workspaces and wikis

> Understand Almanac's ownership and knowledge boundaries.

A workspace is the administrative boundary. A wiki is the knowledge boundary.

```text theme={"theme":{"light":"github-light","dark":"vesper"}}
Workspace
├── members, billing, API keys
└── Wikis
    ├── sources
    ├── pages
    └── jobs
```

## Workspace

Workspaces own membership, plans, API keys, and one or more wikis. API keys are
scoped to a workspace; their permissions determine which operations they can
perform there.

## Wiki

A wiki contains one source library, a readable page tree, topics, and job history.
Its handle combines the workspace slug and wiki slug:

```text theme={"theme":{"light":"github-light","dark":"vesper"}}
acme/company-handbook
```

CLI, SDK, frontend, and MCP users work with this handle. Direct REST routes work
with opaque resource IDs. A local `.almanac.yaml` only points to the hosted wiki;
it does not store the wiki locally.

Apply this model in [Create and link a wiki](/guides/create-select-wiki), or read
[Handles, IDs, and paths](/concepts/identifiers) for the boundary between surfaces.