> 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, upload it here. This can be an image or a PDF, see [PDF backgrounds](#pdf-backgrounds) below.

**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

## PDF backgrounds

Instead of an image, the background can be a PDF. Links in your PDF stay clickable on the parking card. The PDF must be:

* exactly one page
* A4 portrait (210 x 297 mm), exported without bleed
* not protected by a password or restrictions

Keep the middle of the page empty, that's where we add the parking card data and QR code. Parking cards with a PDF background are A4.

After uploading, we check the PDF in the background. The configuration page shows **PDF checked, ready to use** once it's fine, or tells you why the PDF can't be used so you can export it again. While the check is running, reload the page in a moment.


---

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