> 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/attendees.md).
# Attendees
The people in this form that need access to the event
## Index
The index page is a list of all attendees in this form. It contains easy access buttons per attendee to download their ticket or open their personal [checkin page](/event/accreditation/check-in-out.md).
This page has the ability to multi-select many attendees at once and take bulk action. These actions allow you to:
* Add [zones](/event/accreditation/zones.md)
* Add [food & beverages](/event/general/food-and-beverages.md)
* Add [rewards](/event/general/rewards.md)
* Print [wristbands](/event/misc/wristbands.md#on-site-printed-wristbands)
* Remove
### Printing wristbands for a selection
Printing wristbands for a multi-select opens a window that first checks whether your event has a wristband printer that is online. If there is none, we tell you so and print nothing, so you never end up with codes that nobody handed out.
You can choose whether people who **already have an active wristband** should get a new one. If you leave that option unticked, those people are skipped.
While the run is going you see the progress, and when it finishes you get a report of everybody we did not print for, grouped by reason and with their names:
* **no zones** — the person has no zones at all
* **no future visiting days** — all their visiting days are in the past
* **form not approved** — the form of this person still has to be approved
* **already has an active wristband** — only when you left the option above unticked
{% hint style="info" %}
These are the same rules that already applied when you printed one single wristband from somebody's checkin page. The first two reasons only apply if your event does not allow printing without zones or without future days, and the third one only if your list works with approvals and you do not have the permission to print for unapproved forms.
{% endhint %}
Somebody who misses zones **and** days shows up under both reasons, which is why the total number of people not printed is counted separately.
## Creating
Click the "New" button to create one new attendee in this form.
### Many equals
The "Many equals" button allows you to create up to 200 visitors using basic, almost identical data. The only difference between attendees will be the incrementing number next to their name (John Doe 1, John Doe 2, John Doe 3).
### Import
Copy and paste XLS data into the text area to import up to 300 visitors 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
* Optional questions
* Optional food\&beverages
* Optional zones
Afterwards you can import the data in this file and save you a lot of time and many clicks.
## Download tickets
Next to each attendee in the index list you can find a download button for the ticket of that attendee. Or on the top right of your page you can click the 
button to download **all** the tickets of all the attendees in this form at once.
{% hint style="info" %}
The tickets and their download actions will only be visible if a few rules are met:
* The attendee has at least one visiting day
* The attendee is allowed to download a ticket
* The list has tickets enabled
* ...
{% endhint %}
## Send out tickets via email
Another button 
allows you to send all the tickets via email in 1 click. We only send for the same reasons as above, and the presence of a valid email address.
## Editing checked-in attendees
Once an attendee has been checked in, certain fields on their 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/attendees.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.