> 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

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**](/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**](/event/accreditation/lists/forms/attendees.md): A form has many people. They can receive [tickets](/event/accreditation/ticket-configurations.md), answer questions, receive [rewards](/event/general/rewards.md), ...
* [**Vehicles**](/event/accreditation/members/vehicle.md): A form also has many vehicles. These can receive [parking cards](/event/accreditation/parking-card-configurations.md), [tags](/event/general/tags.md), ...


---

# 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.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.
