> 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/users.md). # Users See who in your organization has Dispatch, invite colleagues, set each person's allowance and guardrail, and remove access Everyone who uses Dispatch needs two things from an administrator: access, and the limits they'll work within. **The Users page is where a Dispatch Admin sees who in the organization has Dispatch, invites colleagues and removes access.** Each person's allowance and guardrail are set alongside their keys on the API Keys page, and this page explains both. {% hint style="info" %} **Who can use it**: The Users page is for Dispatch Admins only. Open it from **Manage** in the sidebar, or from **Users** in the account menu at the top right. See [Roles & Access](/dispatch/get-started/roles-and-access.md). {% endhint %} ## The People List The list shows everyone in your organization with a DarcyIQ login, including people who don't have Dispatch. The header gives the totals, for example "24 people in this organization with a Darcy login, 9 with Dispatch." | Column | What it shows | | ------------ | ------------------------------------------------------------------------------ | | **Person** | Name and email | | **Dispatch** | **Licensed** if they hold a Dispatch seat, otherwise **No licence** | | **Role** | **Dispatch User**, **Dispatch Admin**, or a dash if they have no Dispatch role | | **Status** | **Active**, or **Invited** for an invitation that hasn't been accepted yet | Click a column heading to sort by it. ### Finding People | Control | What it does | | --------------------------- | -------------------------------------------------------------------------------------------------- | | **Search by name or email** | Searches the whole organization once you've typed two characters | | **Access** | **Has Dispatch** (the default), **Everyone**, or **No Dispatch access** | | **Role** | **Any role**, **Dispatch Admin** or **Dispatch User** | | **Status** | **Any status**, **Active** or **Invited** | | **Table** / **Cards** | Switches between a sortable table and a card view. Dispatch remembers your choice in that browser. | The page loads the first 100 people. In a larger organization, use the search to find anyone beyond them. ## Inviting a Colleague {% stepper %} {% step %} **Click Invite a colleague** It's at the top of the Users page. Dispatch Admins also have an **Invite** button on [Overview](/dispatch/use-dispatch/overview.md). {% endstep %} {% step %} **Enter their details** Fill in **First name**, **Last name** and **Work email**. All three are required. {% endstep %} {% step %} **Choose their Dispatch role** Under **Dispatch role**, choose **Dispatch User** (the default) or **Dispatch Admin**. "A Dispatch User creates and manages their own keys. A Dispatch Admin sees the whole organization's keys, budgets and policy." {% endstep %} {% step %} **Click Send invitation** They get a DarcyIQ login with Dispatch waiting. Dispatch confirms that they "will have Dispatch waiting when they set their password." {% endstep %} {% endstepper %} ### When a Seat Is Refused Each person with Dispatch uses a Dispatch seat, and seats are managed in the DarcyIQ Platform. The account can be created even when no seat is free, for example if your seats filled up after you opened the form. In that case, Dispatch tells you the person "was invited, but the Dispatch licence was refused. Check your seats in Darcy Platform." Free up or add a seat in the DarcyIQ Platform. ### People Who Already Have a DarcyIQ Login The invitation is for people who are new to DarcyIQ. To give Dispatch to somebody who already has a DarcyIQ login, use the DarcyIQ Platform, where the rest of their access is shown alongside it. ## Setting a Person's Allowance and Guardrail A person's **allowance** is the most they can spend, and their **guardrail** is the policy their requests follow. Both belong to the person, not to a key. Every key they hold draws on the same allowance and follows the same guardrail, so creating another key never gives anyone more to spend. Only a Dispatch Admin can change them. ### What New People Start With A person's allowance and guardrail are set when they get their first key, whether they create it themselves or you create it for them. They come from **Defaults for new key owners** on the [Guardrails](/dispatch/manage/manage/guardrails.md#member-defaults) tab of the Organization page. Changing the defaults later doesn't change anyone who already has a key. ### Changing One Person's Allowance Allowances are changed on the [API Keys](/dispatch/use-dispatch/api-keys.md) page, where a Dispatch Admin sees every key in the organization grouped by owner. {% stepper %} {% step %} **Find the person's keys** The **Owner budget** column shows, once per person, what they've spent against their limit, for example "$42.00 / $100.00 per month", with a progress bar. {% endstep %} {% step %} **Click Change budget** The **Budget for** panel opens. It "Applies to every key they hold, now and later." {% endstep %} {% step %} **Set the limit, reset and guardrail** Enter a **Spend limit (USD)** greater than zero, or clear it to lift the cap entirely. Choose how often it **Resets**: **daily**, **weekly** or **monthly**. Under **Guardrail**, choose one of your guardrails or **None**. Each person has one guardrail at most. {% endstep %} {% step %} **Click Save budget** The change takes effect on the person's next request. {% endstep %} {% endstepper %} {% hint style="warning" %} **Spend is measured every few minutes.** A person can go slightly past their limit before Dispatch starts refusing their requests. Once they're refused, the error tells them their budget has been reached, how much they've spent, and that it resets at the start of the next period or an administrator can raise it. {% endhint %} A person's allowance sits inside the organization budget. Even with allowance left, nobody can make requests once the organization budget is reached. See [Billing & Budget](/dispatch/manage/manage/billing-and-budget.md#how-the-budget-relates-to-allowances). ## Viewing a Person's Keys A person's keys are listed on the [API Keys](/dispatch/use-dispatch/api-keys.md) page, grouped under their name in the **Key owner** column. For someone with more than one key, it says how many, for example "3 keys, one budget." Each key shows its label, its spend over the last 30 days, and its tags. A key owner doesn't have to be a person. A key for a nightly job or a shared service can be owned by the job itself, so it has its own allowance instead of spending from whoever set it up. ## Pausing or Revoking a Key To stop a single key without affecting the person's other keys, use the **Active** switch beside it on the API Keys page. A paused key is refused from its next request and can be switched back on. To get rid of a key for good, click the bin icon to revoke it. ## Removing Dispatch From Someone On the Users page, hover over a person with a **Licensed** badge and click the remove icon at the end of their row. What happens depends on their status: | Status | What removing does | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Active** | They lose Dispatch immediately. Their keys stop working, and their spend stays on the books. Their DarcyIQ login and any other products are untouched. | | **Invited** | Their invitation is withdrawn. They can't use Dispatch, and the email they were sent stops working. Their DarcyIQ login is left alone. | ## Next Steps | Goal | Documentation | | ----------------------------------------------------- | ----------------------------------------------------------------- | | Set the allowance and guardrail new people start with | [Guardrails](/dispatch/manage/manage/guardrails.md) | | Set the organization-wide ceiling | [Billing & Budget](/dispatch/manage/manage/billing-and-budget.md) | | Manage keys for yourself and others | [API Keys](/dispatch/use-dispatch/api-keys.md) | | Understand what each role can do | [Roles & Access](/dispatch/get-started/roles-and-access.md) | --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.darcyiq.com/dispatch/manage/users.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.