> 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/lists/forms/vehicles.md). # Vehicles ### Index The index page is a list of all vehicles in this form. It contains easy access buttons per vehicle to download their parking card. This page has the ability to multi-select many vehicles at once to remove them. ### New Click the "New" button to create one new attendee in this form. ### Import Copy and paste XLS data into the text area to import up to 300 vehicles at once. On this screen there is a detailed explanation of how the XLS should be structured. You can download an example XLS that will be generated when you request it. This example includes all the required data needed to import (driver name, phone number, ...). Afterwards you can import the data in this file and save you a lot of time and many clicks. ## Download parking cards Next to each vehicle in the index list you can find a download button for the parking card of that vehicle. Or on the top right of your page you can click the button to download **all** the parking cards of all the vehicles in this form at once. {% hint style="info" %} The download actions will only be visible if a few rules are met: * The vehicle has at least one visiting day * The list has parking cards enabled * ... {% endhint %} ## Send out parking cards via email Another button allows you to send all the parking cards via email in 1 click. We only send for the same reasons as above, and the presence of a valid email address. ## Custom parking card configuration per vehicle If your list has multiple parking card configuration configured, you can assign a specific design to an individual vehicle from its detail page. This overrides the list's default parking card configuration for that vehicle only. ## Editing checked-in vehicles Once a vehicle has been checked in, certain fields on its record become read-only. A notice will inform you when this is the case. This protects the integrity of your check-in data. --- # 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/lists/forms/vehicles.md?ask=&goal= ``` `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.