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

# Playbooks

> Outcome-shaped playbooks for the teams that run Ravenna: IT, HR and People, Finance, Legal, Security, and RevOps, plus the cross-team setups every desk needs.

[Day one](/guides/day-one/overview) is the first playbook, and it gets one desk live. The rest take it from there: each one is a complete setup for a real team, written as a sequence of decisions rather than a feature tour.

Pick the department you are launching. If you are launching two, do them one at a time, a week apart.

## By department

<CardGroup cols={2}>
  <Card title="IT" icon="laptop" href="/guides/playbooks/it/overview" horizontal>
    Help desk, software access, and device lifecycle.
  </Card>

  <Card title="HR and People" icon="users" href="/guides/playbooks/hr/overview" horizontal>
    A private-by-default desk, onboarding, and offboarding.
  </Card>

  <Card title="Finance" icon="receipt" href="/guides/playbooks/finance/overview" horizontal>
    Purchase approvals, expenses, and vendor invoices.
  </Card>

  <Card title="Legal" icon="scale" href="/guides/playbooks/legal/overview" horizontal>
    Contract review and policy questions.
  </Card>

  <Card title="Security" icon="shield" href="/guides/playbooks/security/overview" horizontal>
    Incident intake and access reviews.
  </Card>

  <Card title="RevOps and Sales Ops" icon="chart-line" href="/guides/playbooks/revops/overview" horizontal>
    Deal desk and go-to-market tooling.
  </Card>
</CardGroup>

## Cross-team setups

These are not owned by one department. Every desk reaches for them eventually, so they live on their own.

<CardGroup cols={2}>
  <Card title="Approval flows" icon="check-check" href="/guides/playbooks/approval-flows" horizontal>
    Templates, rounds, and dynamic approvers.
  </Card>

  <Card title="Launch the Portal" icon="globe" href="/guides/playbooks/launch-the-portal" horizontal>
    A web entry point for people who are not in Slack.
  </Card>

  <Card title="Email support" icon="mail" href="/guides/playbooks/email-support" horizontal>
    Point an existing shared inbox at a channel.
  </Card>

  <Card title="SLAs and business hours" icon="timer" href="/guides/playbooks/slas-and-business-hours" horizontal>
    Response targets measured against a real working week.
  </Card>

  <Card title="Reporting and briefs" icon="chart-column-big" href="/guides/playbooks/reporting-and-briefs" horizontal>
    Dashboards, CSAT, and a weekly brief in Slack.
  </Card>
</CardGroup>

## What every playbook assumes

Each one opens with its own prerequisites, but they all share these:

* One workspace per team, not per topic. A workspace is where a team's channels, forms, categories, and members live.
* A finished [Day one](/guides/day-one/overview) track for at least one desk, so you have seen the pieces fit together once.
* Someone who owns the desk. Playbooks describe setups, not staffing, and an unowned desk goes stale in a month.

<Callout icon="link" color="#6B7280">Learn more about [how workspaces map to teams](/documentation/platform/workspaces/overview)</Callout>

## Choosing your first department

If you are still deciding, the usual order is IT, then HR, then everyone else. IT has the highest volume of repetitive, documented requests, which is exactly what the agent is good at, and it gives you an internal reference customer before you ask a more sensitive team to trust the tool.

Start elsewhere when the pain is obviously elsewhere. A Finance team drowning in purchase approvals over email will get more out of week one than an IT team that already has a functioning process.


## Related topics

- [Guides](/guides/overview.md)
- [IT help desk](/guides/playbooks/it/help-desk.md)
- [Device lifecycle](/guides/playbooks/it/device-lifecycle.md)
- [Employee lifecycle architecture](/guides/playbooks/hr/employee-lifecycle.md)
- [Incident intake](/guides/playbooks/security/incident-intake.md)