> For the complete documentation index, see [llms.txt](https://docs.darcyiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darcyiq.com/dispatch/manage.md).

# Manage 🏢

- [Organization Settings](https://docs.darcyiq.com/dispatch/manage/manage.md): The Organization page, where a Dispatch Admin sets spend, content policy, models, data residency, tags and provider accounts for everyone at once
- [Billing & Budget](https://docs.darcyiq.com/dispatch/manage/manage/billing-and-budget.md): Prepaid credits that fund your organization's usage, and the organization budget that caps what everyone can spend in a day, week or month
- [Guardrails](https://docs.darcyiq.com/dispatch/manage/manage/guardrails.md): Named policies that cap what people can spend, block requests carrying sensitive content, and narrow which models they can call, plus the defaults every new key owner starts with
- [Model Access](https://docs.darcyiq.com/dispatch/manage/manage/model-access.md): Choose which model tiers everyone in your organization may call, and whether tiers added later arrive switched on or off
- [Data Residency](https://docs.darcyiq.com/dispatch/manage/manage/data-residency.md): Choose where requests from everyone in your organization may be processed, and see which models a region would cost you before you switch
- [Tags](https://docs.darcyiq.com/dispatch/manage/manage/tags.md): Define the tags spend is grouped by, from tags people put on their keys to tags Dispatch applies automatically by reading each conversation
- [Provider Keys](https://docs.darcyiq.com/dispatch/manage/manage/provider-keys.md): Use your own OpenAI, Anthropic, Azure or Amazon Bedrock account for that provider's traffic instead of DarcyIQ's
- [Users](https://docs.darcyiq.com/dispatch/manage/users.md): See who in your organization has Dispatch, invite colleagues, set each person's allowance and guardrail, and remove access


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.darcyiq.com/dispatch/manage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.