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

# Rollout plan

> A phased plan for introducing Sidekick to your company.

Sidekick has a lot of admin surface: people, access, governance, budgets, branding, chat surfaces, and monitoring. You don't have to configure all of it before anyone can use Sidekick, but a fixed order gets you to a safe, working rollout with the least backtracking.

## Recommended order

<Steps>
  <Step title="Add people">
    Bring your team onto the roster first. Nobody can sign in to Sidekick until they're added as a person.
  </Step>

  <Step title="Set access">
    Turn on single sign-on so people authenticate with your identity provider, and turn on directory sync so login access follows who's actually on the roster.
  </Step>

  <Step title="Approve models, connectors, and skills">
    Decide what agents are allowed to run before you open Sidekick up. This bounds what a thread can do from day one, instead of you reacting to it later.
  </Step>

  <Step title="Set budgets">
    Put spend limits in place across people and projects before usage ramps up, so cost stays bounded as more people start running work.
  </Step>

  <Step title="Brand it">
    Apply your company's logo, colors, and fonts so Sidekick reads as an internal tool rather than a third-party app.
  </Step>

  <Step title="Connect a chat surface">
    Connect the chat platform your company already uses so people can reach Sidekick from where they work, not just from a dedicated app.
  </Step>

  <Step title="Monitor with approvals and audit">
    Once people are working in Sidekick, use approvals and the audit record to see what's running and confirm it's staying inside the rules you set.
  </Step>
</Steps>

<Note>
  This order isn't enforced. You can, for example, brand Sidekick before you set budgets. But governing models, connectors, and skills before people have broad access avoids opening the door wider than you meant to.
</Note>

## Set up each step

### Roll out and access

<CardGroup cols={2}>
  <Card title="People" icon="users" href="/docs/sidekick/admin/people">
    Add people to Sidekick, enable or disable their access, and manage activation.
  </Card>

  <Card title="SSO" icon="fingerprint" href="/docs/sidekick/admin/sso">
    Connect Sidekick to your identity provider so people sign in with company credentials.
  </Card>

  <Card title="Directory sync" icon="refresh-cw" href="/docs/sidekick/admin/directory-sync">
    Keep Sidekick login access in sync with your identity provider automatically.
  </Card>
</CardGroup>

### Govern what agents can do

<CardGroup cols={2}>
  <Card title="Govern models" icon="cpu" href="/docs/sidekick/admin/govern-models">
    Set which models are available and how they're used.
  </Card>

  <Card title="Govern tools and connectors" icon="plug-zap" href="/docs/sidekick/admin/govern-tools-connectors">
    Control which tools and connectors agents are allowed to use.
  </Card>

  <Card title="Govern skills" icon="wand-sparkles" href="/docs/sidekick/admin/govern-skills">
    Approve and manage the skills available across your workspace.
  </Card>

  <Card title="Budgets" icon="wallet" href="/docs/sidekick/admin/budgets">
    Set spend limits and track usage across people and projects.
  </Card>
</CardGroup>

### Brand it and connect a chat surface

<CardGroup cols={2}>
  <Card title="Branding" icon="palette" href="/docs/sidekick/admin/branding">
    Apply your company's logo, colors, and fonts to Sidekick.
  </Card>

  <Card title="Slack" icon="hash" href="/docs/sidekick/admin/slack">
    Connect Sidekick to your company's Slack workspace.
  </Card>
</CardGroup>

### Monitor

<CardGroup cols={2}>
  <Card title="Approvals" icon="shield-check" href="/docs/sidekick/admin/approvals">
    Configure which actions require approval before they run.
  </Card>

  <Card title="Audit" icon="scroll-text" href="/docs/sidekick/admin/audit">
    Review a record of the actions people and agents have taken.
  </Card>
</CardGroup>