> ## 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.

# Approvals

> Configure which actions require approval before they run.

Open **Sidekick → Approvals** to work the admin queue: every tool approval, admin approval, and budget request waiting on a decision.

## What lands in the queue

<CardGroup cols={3}>
  <Card title="Tool approvals" icon="plug-zap">
    A connector call that hit a gate requiring admin sign-off, beyond whatever consent the person running the thread already gave.
  </Card>

  <Card title="Admin approvals" icon="shield-check">
    An action a member can't clear on their own, regardless of which tool is involved.
  </Card>

  <Card title="Budget requests" icon="wallet">
    A request to raise a spend cap that a person or agent has hit. See [Budgets](/docs/sidekick/admin/budgets).
  </Card>
</CardGroup>

## Approve or deny

<Steps>
  <Step title="Open an item">
    Each item in the queue shows what's being asked for, who or what it's for, and a risk recommendation describing why it needs a decision.
  </Step>

  <Step title="Read the risk recommendation">
    The risk recommendation is a summary of what makes this item worth a second look, not an automatic decision. It's there to inform your call, not replace it.
  </Step>

  <Step title="Approve or deny">
    Approving clears the item and lets the underlying action proceed. Denying blocks it. Either way, the person or thread it came from is notified of the outcome.
  </Step>
</Steps>

<Note>
  Approving a tool or admin approval doesn't resume the thread automatically. The person in the thread still presses Continue on their end.
</Note>

## Where to go next

<CardGroup cols={2}>
  <Card title="The governance model" icon="shield-check" href="/docs/sidekick/concepts/governance-model">
    How consent gates and admin approval work together to keep sensitive actions in bounds.
  </Card>

  <Card title="Approvals" icon="check-check" href="/docs/sidekick/use/approvals">
    What an approval card looks like from the member's side, and how they respond to it.
  </Card>
</CardGroup>