> 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/parking-card-configurations.md).

# Parking card configurations

All parking cards that are generated on Eventication are customisable. There are a bunch of settings you can adjust to create pretty looking parking cards.

**Title**: Give the parking card a default title.

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

**Background**: If you want to use a parking card background, it here

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

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


---

# 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/parking-card-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.