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

# Artist portal

The artist portal lets the artist's own people work on their show **without an account**: each event artist gets a personal secret link.

**Invites**: the invite mail (subject and text per language in the [settings](https://docs.eventication.com/event/artists/settings.md)) is sent to the artist's contacts that have portal access. Sending an invite mints the link.

**What the artist sees**: their details, offers and offer documents, the advancing checklist with the items they can fill in themselves, their riders (upload documents, read your feedback), accommodation, transports, stage information and documents, itinerary and briefing.

**Edit window**: a portal closes for edits on its end date, a default for the event that can be overridden per artist.

{% hint style="warning" %}
Portal links are secrets: anyone with the link can open it. A duplicated event never copies them; a new edition mints new links.
{% 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/artist-portal.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.
