> 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/accreditation/ticket-configurations.md).

# Ticket configurations

Using our platform you can generate tickets for your visitors. This page allows you to configure all those different tickets. There are a bunch of settings you can adjust to create pretty looking tickets.

**Internal title**: Give this ticket a name. This value is never shown outside of the moderator section. Just an identifier.

**Use ticket background?**: This checkmark will define if you would like to use a full-size background for the ticket. This will cover the whole back side of the ticket.

**Ticket background**: If you want to use a ticket background, it here

**Banner**: If you don't want to use the ticket background, you can upload a banner that will be shown on the top of the ticket

**Map**: Upload an image of the map you would like to show on the ticket (optional)

**Description**: Add a description that will be shown after the map

{% hint style="success" %}
This text area supports [formatting](/event/misc/text-formatting.md).
{% endhint %}

**Map and description on new page?**: This allows you to add a bigger map and more description text on a new page after the ticket

{% hint style="info" %}
A new page will always be "true" if you use a ticket background.
{% endhint %}

On the op of the page there are buttons to add a new configuration, edit an existing one, generate a preview or delete a configuration.

{% hint style="danger" %}
Before deleting a ticket configuration the platform will require you to migrate the dependencies to another ticket configuration. This ensures current lists can keep downloading their tickets.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eventication.com/event/accreditation/ticket-configurations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.