---
title: "Guides by role"
description: "Start from your role: operator, team lead, admin and IT, developer, AI agent or security reviewer."
url: "https://docs.octo.ad/guides/"
id: "guides"
type: "map"
audience: "operator"
dateModified: "2026-11-06"
keywords: ["guides"]
---

# Guides by role

> Start from your role: operator, team lead, admin and IT, developer, AI agent or security reviewer.

Each guide is a short procedure. It links to the pages it draws on, so nothing has to be read twice.

- [For the operator: your first steps](/guides/operator-first-week/): The first decisions to make as the person who runs OCTOPUS: a workflow, a rule, a team, an owner, and who may switch it off.
- [For a team lead: send decisions to a person](/guides/team-lead-send-decisions-to-a-person/): Choose which decisions reach a person and which follow a rule your people agreed.
- [For admin and IT: approve a connection](/guides/admin-approve-a-connection/): Work through the one-page review sheet before any source or agent connects.
- [For a developer: connect an agent](/guides/developer-connect-an-agent/): Point an MCP client at the public endpoint and ask a question. No account is needed.
- [For an AI agent reading these docs](/guides/for-ai-agents/): How an agent should read, cite and route: llms.txt, markdown twins, typed JSON-LD, and what is not published.
- [For a security reviewer: what to ask to see](/guides/security-reviewer/): The trust claims one by one, and what to ask to see for each before a trial.