> 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.md).

# Lists

People with access to your event, without a user account

Our lists module allows you to invite people, companies, groups, ... to your event without the need to create an account with a password. Almost all our events use this feature heavily.

The lists module work in a tree structure.

* **List**: The object that you use to group visitors. Some examples out events use:
  * Sponsors
  * Suppliers
  * Guests Friday
  * VIPS
* [**Forms**](https://docs.eventication.com/event/accreditation/lists/forms.md): A list has many forms. A form can be a company, or just a group of people. Some examples of a form:
  * The local dance group
  * A company that visits the event
  * Guests of the organiser
* [**People**](https://docs.eventication.com/event/accreditation/lists/forms/attendees.md): A form has many people. They can receive [tickets](https://docs.eventication.com/event/accreditation/ticket-configurations.md), answer questions, receive [rewards](https://docs.eventication.com/event/general/rewards.md), ...
* [**Vehicles**](https://docs.eventication.com/event/accreditation/members/vehicle.md): A form also has many vehicles. These can receive [parking cards](https://docs.eventication.com/event/accreditation/parking-card-configurations.md), [tags](https://docs.eventication.com/event/general/tags.md), ...

{% hint style="info" %}
Two lists can also be created and filled by the artists module: the artist crew list and the artist guest list, configured under the module's [settings](https://docs.eventication.com/event/artists/settings.md). They appear here like any other list, but their entries are managed from the artists pages.
{% 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 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/lists.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.
