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

# What it's for

The dashboard is Kira for people. Your integration talks to the API; the people in your organisation who need to look something up, answer a compliance request or make a one-off payment use the dashboard instead of asking an engineer.

It runs on the same API you build against — the same sub-clients, the same accounts, the same payouts. Nothing exists only in one and not the other.

## What people use it for

|                                 |                                                                                                                                                                              |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Look something up**           | A customer, an account, a payment. Read-only, and the fastest way to answer "where is that money"                                                                            |
| **Answer a compliance request** | Requests for information arrive here as well as on your webhook, and can be answered here — usually the right route when the answer is a document your compliance team holds |
| **Make a payment by hand**      | A one-off payout without going through your product                                                                                                                          |
| **Complete an onboarding**      | Supply what a business still needs when the information did not come through your own flow                                                                                   |

## When to use which

**Build it into your product** when it happens often, has to be fast, or your customer should never know Kira is involved. That is the API.

**Do it in the dashboard** when it is occasional, needs a person's judgement, or the person doing it is not an engineer. Answering a compliance request is the clearest example: the information usually sits with your finance or compliance team, not in your product's database.

<Note>
  Both surfaces produce the same events. A payout made in the dashboard reaches your webhook exactly like one made through the API, so your integration does not need to know which was used.
</Note>

<Card title="Access" icon="arrow-right" href="/dashboard/access">
  Who gets in, and how.
</Card>