> 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.md).
# Forms
A list has many forms. A form can be a company or just a group of people. This page is an overview of all forms in this list. /
{% hint style="info" %}
If you have [self-registration](/event/accreditation/lists/registration.md) and approval turned on, the page is divided in 4 different pages:
* **Approved**: The approved forms
* **Rejected**: The rejected forms
* **Submitted**: The submitted forms (need to be approved or rejected)
* **Not submitted**: The forms that have been self-registered, but haven't submitted their application yet.
This will also show some checkboxes that enable you to approve/reject multiple forms in one click.
{% endhint %}
 Allows you to bulk import forms from an XLS file.
{% hint style="info" %}
The import page lists the columns of your file in two groups: the ones that are **required**, and the ones that are **optional**. You can leave optional columns out of your file completely, or leave them empty.
One of the optional columns is the **form description**, so you can import the description of every form together with the rest of its data. The example XLS you can download on that page contains the description column as well, so you can see exactly where it goes.
{% endhint %}
 Allows you to access different data-export functions.
 Allows you to send all the forms an email to their responsible email address with their secret URL.
{% hint style="info" %}
The email indicator can have 3 statuses
* 
This form hasn't been notified yet
* 
This form doesn't have a (valid) email address
* 
This form has been notified
{% endhint %}
The index of forms indicates [self-registered](/event/accreditation/lists/registration.md) forms with a badge 
.
---
# 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/forms.md?ask=&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.