> 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/settings.md).

# Settings

Everything the module does is switched and configured here, per event.

**Feature switches**: offers, advancing, riders, rider feedback, dressing rooms, accommodation, transport, stage names per day, docks, runsheet, itinerary, briefing, finance, tasks, artist types and the artist portal can each be switched off. All of them start **on**.

**E-mail texts**: the offer mail, the advancing reminder mails and the portal invite, each per language.

**Artist types**: the type labels with their defaults: accreditation and guest maximums, needs accommodation / transport / flight. Defaults are copied onto an artist once, when they join the event; editing a type later never rewrites artists, it only flags the ones that now differ.

**Advancing checklist**: the phases and items every performance's dossier starts from, with fixed or relative deadlines.

**Briefing blocks**: the venue, parking and contacts texts every artist briefing shares.

**Accreditation**: which lists the module's accreditation lands on, split between crew and guests.

{% hint style="info" %}
Switching a feature off is a curtain, not a reset: the pages disappear, the data stays, and switching it back on shows everything as it was.
{% 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/settings.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.
