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

# Information

Book artists, advance their shows and run the artist side of your event.

The artists module runs the artist side of an event, from the first wishlist name to the last ride home. [Artists](https://docs.eventication.com/event/artists/artists.md) are shared across your whole company; everything else lives per event.

**Booking**: build the [line-up](https://docs.eventication.com/event/artists/line-up.md) per stage and day, and send [offers](https://docs.eventication.com/event/artists/offers.md).

**Preparing**: each performance has an [advancing](https://docs.eventication.com/event/artists/advancing.md) dossier with its checklist, [riders and feedback](https://docs.eventication.com/event/artists/riders.md), itinerary and briefing. The [artist portal](https://docs.eventication.com/event/artists/artist-portal.md) lets the artist's own people fill in their part without an account.

**Logistics**: [purchasing](https://docs.eventication.com/event/artists/purchasing.md) turns the rider lines into order forms per [supplier](https://docs.eventication.com/event/artists/suppliers.md), with [rider products](https://docs.eventication.com/event/artists/rider-products.md) as your catalog. [Stages](https://docs.eventication.com/event/artists/stages.md) carry documents, docks and the runsheet; [dressing rooms](https://docs.eventication.com/event/artists/dressing-rooms.md), [accommodation](https://docs.eventication.com/event/artists/accommodation.md) and [transport](https://docs.eventication.com/event/artists/transport.md) cover where everybody sleeps, changes and drives.

**Running it**: [tasks](https://docs.eventication.com/event/artists/tasks.md) for the loose ends, [finance](https://docs.eventication.com/event/artists/finance.md) for the money, and [settings](https://docs.eventication.com/event/artists/settings.md) to switch each part on or off per event. Everything starts on.

{% hint style="info" %}
What a moderator can see and do in the module is controlled per moderator: viewing, editing artists and stages, offers and finance (money) rights are separate.
{% endhint %}


---

# 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.eventication.com/event/artists/information.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.
