> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/get-started.md).
# Get started
Set up your workspace and help your team start booking.
Set up the people and meeting settings first, then build your first workflow.
## Choose your guide
Admin setup
Connect your tools, prepare routing and publish your first flow.
## Find your way around
| Open in the sidebar | Use it for |
| -------------------- | ---------------------------------------------------------------------------------- |
| **Queues** | Queues, Routing profiles, Rulebooks, Fit score, Assignment log, and Routing audit. |
| **Workflows** | The workflow builder and its Logs. |
| **Lead forms** | Hosted and embedded forms, publication, and submissions. |
| **Event types** | Reusable meeting configuration and event hosts. |
| **Booking links** | Personal links and your booking page. |
| **Bookings** | Scheduled, completed, cancelled, and no-show meetings. |
| **Field catalog** | Person fields, company fields, and enrichment chains. |
| **Website tracking** | Your website snippet, tracking settings, and captured website activity. |
Your role and workspace activation determine which areas you can open.
For your first setup, use one queue, one event type, and one workflow. Once that flow works, add ownership matching, qualification, enrichment, and follow-up actions.
## More guides
* [Feature availability](/get-started/availability.md)
* [Distro glossary](/get-started/glossary.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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.distro.so/get-started.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
