# systemHUB Docs

> Machine-readable documentation for connecting AI agents and technical users to systemHUB.

systemHUB is a platform for documenting, organising, and training teams on business systems — **Systems** (procedures/SOPs), **Policies** (compliance documents), and **Trainings** (learning modules). This documentation set describes how an AI agent (via the systemHUB MCP server) or a developer can connect to systemHUB, read a company's content, and author or maintain it programmatically.

This is the **AI-facing** surface. If you're a human looking for friendly, task-oriented help, use [help.systemhub.com](https://help.systemhub.com) instead. The two layer together — they don't replace each other.

## Who this is for

- **A prospect's or customer's AI assistant** connecting to systemHUB via MCP, so it can find and use the company's systems with no friction.
- **Technical users / developers** integrating with, or building on top of, the systemHUB MCP server.

## Start here

1. **[Getting started](/docs/getting-started)** — connect the systemHUB MCP server and make your first call.
2. **[Quick wins](/docs/quick-wins)** — verified copy-paste prompts for a newly connected agent.
3. **[Document lifecycle](/docs/concepts/document-lifecycle)** — how documents, states, and publishing work.
4. **[Roles & seats](/docs/concepts/roles-and-seats)** — how access is granted and counted.
5. **[Authoring content](/docs/concepts/authoring-content)** — the formatting contract: what survives the editor and what gets stripped.
6. **[Errors & limits](/docs/concepts/errors-and-limits)** — known failure modes and validation limits, stated up front.
7. **[Tool reference](/docs/tool-reference)** — every MCP tool, its inputs, and what it returns, generated from the live schema.

## Guides (worked examples)

Task-oriented walkthroughs with request→response examples:

- **[Draft an SOP into systemHUB](/docs/guides/drafting-sops)** — orient, dedupe, create to the house format, attach templates/media, version.
- **[Audit access, sign-off & training](/docs/guides/auditing-access)** — who can see what, who's agreed, who's completed training, what a person owns.
- **[Organise & maintain the library](/docs/guides/organising-content)** — folders, moves, states, tags, learning tracks, master templates.

## What you can do through the MCP today

- **Discover & read** — browse the folder tree; search systems, policies, and trainings by name; read full document content, owners, tags, media, and attachments.
- **Audit** — see who a document is assigned to (members & roles), agreement/sign-off status, and training completion progress.
- **Author & maintain** — create, edit, move, and publish systems, policies, trainings, folders, learning tracks, tags, and media.

## Known limits

These are documented honestly so a connecting agent doesn't try what isn't there yet:

- **No write-side user/seat management** via the MCP — members and seat allocation are managed in the app UI.
- **No usage / "who-viewed-what-when" telemetry** via the MCP yet.
- **Images cannot be injected via the API** — they're uploaded through the editor. See [Authoring content](/docs/concepts/authoring-content).

## For AI agents reading this

Every page on this site is also servable as plain markdown — append `.md` to the page URL (e.g. [/docs/getting-started.md](/docs/getting-started.md)). A machine-readable index lives at [/llms.txt](/llms.txt).