> 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/get-started/opening-dispatch.md).

# Opening Dispatch

How to open Dispatch from the DarcyIQ Platform launcher, and how signing in and out works

Dispatch doesn't have its own login page. **You open it from the DarcyIQ Platform launcher**, the same place you open the rest of the platform's products, and it signs you in with your DarcyIQ account.

{% hint style="info" %}
**Dispatch has to be part of your organization's plan.** If your organization has Dispatch, its card appears in the launcher with a **Launch** button. If you don't see it, ask your administrator.
{% endhint %}

## Launching Dispatch

{% stepper %}
{% step %}
**Sign in to the DarcyIQ Platform** Go to the launcher and sign in with your DarcyIQ account.
{% endstep %}

{% step %}
**Click Launch on the Dispatch card** The launcher hands you over to Dispatch, which opens already signed in. There's no second login.
{% endstep %}

{% step %}
**Accept the terms and take the tour (first visit only)** The first time you open Dispatch, you're asked to accept its terms, and a setup guide may open to walk you through getting started.
{% endstep %}

{% step %}
**Start where your role starts** Administrators open on [Overview](/dispatch/use-dispatch/overview.md), because the first question an administrator usually has is what Dispatch is costing. Everyone else opens on [API Keys](/dispatch/use-dispatch/api-keys.md), because your Overview stays empty until you have a key.
{% endstep %}
{% endstepper %}

## Staying Signed In

Reloading the page keeps you signed in. Dispatch keeps your session for the browser tab it was launched in. If you open Dispatch's address in a new window or a bookmark, Dispatch sends you to the DarcyIQ Platform to sign in, or straight back through the launcher if you're already signed in there, and then returns you to Dispatch.

## Signing Out

**Sign out** in the account menu ends your DarcyIQ session, not just your Dispatch tab. You'll be returned to the launcher signed out, so the next person at the keyboard can't reopen Dispatch, or any other DarcyIQ product, as you.

## Light and Dark Mode

Use the theme toggle in the top right to switch between light and dark mode. Dispatch remembers your choice in that browser.

## Next Steps

| Goal                                     | Documentation                                               |
| ---------------------------------------- | ----------------------------------------------------------- |
| Understand what your role lets you do    | [Roles & Access](/dispatch/get-started/roles-and-access.md) |
| Create a key and make your first request | [Quickstart](/dispatch/get-started/quickstart.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 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/get-started/opening-dispatch.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.