> 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/scheduling/event-types.md).

# Event types and hosts

An event type defines the reusable meeting settings used by links and workflow schedulers.

**Open Event types.** Create a meeting or edit an existing event before selecting it in Show Scheduler.

## Configure the meeting

Set the meeting name, duration, location, booking questions, and availability settings. Review notice periods, buffers, and the booking window supported by the event.

Choose conferencing where needed and verify the host has connected the relevant account.

Use the preview to review the calendar, questions, and confirmation. A preview does not create a real booking or confirm provider delivery.

## Configure Hosts

In **Hosts**, choose the **Event kind** and **Primary host**.

* A **solo** event has one host.
* A **shared** event adds required and optional co-hosts.

The primary host can be a member or a queue. A queue uses its routing profile when selecting the meeting host.

Add **Required co-hosts** when everyone must attend; their availability limits the offered times. Add **Optional co-hosts** when they should be invited without limiting the times.

**Always invite** adds fixed email invitees without checking their calendars. It supports up to 10 addresses.

## Use the event in a workflow

In **Show Scheduler**, choose the event type and set **Hosts**.

**Use event hosts** follows the event's configured primary host and co-hosts. Host changes there apply without republishing the workflow.

**Choose hosts here** uses the sources configured in the workflow step. Use it when that flow should follow its routed owner rather than the event's default host.

## Review shared changes

An event type can be used in multiple journeys. Check where it is used before changing its hosts, questions, or timing settings.

To offer more times across a pool, use a queue host with **Any available member**. To offer one person's times, use a member or earlier assignee.

## Add meeting messages

Configure **Messages** for status notifications and reminders. Review the templates and recipients so they do not duplicate workflow notifications.

See [Meeting messages](/scheduling/messages.md) and [Calendars and availability](/scheduling/availability.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/scheduling/event-types.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 `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.