> For the complete documentation index, see [llms.txt](https://docs.eventflowapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventflowapp.com/eventflow-cms/eventflow-reports/form-reports/form-submission.md).

# Form Submission

From here, you can see exactly who has submitted, when, and export the results for offline use. Clicking on a form submission will reveal the submitted data and allow you to edit the submission.

### **Filters**

**Team Type** – refine submissions by team type, e.g. exhibitor, sponsor, or any other team types you have created.

{% hint style="info" %}
Filters automatically update the displayed entries and also apply to the exported data, so you only download the results you need. Great for only exporting a particular team type.
{% endhint %}

### **Form Entries List**

Each row in the list shows:

* **Team name** – the organisation that submitted the form
* **Submitted By** – the individual who completed the form.
* **Submission Date** – when the entry was made.

{% hint style="info" %}
Results are automatically sorted by data, but you can toggle the order by clicking on 'Submitted' at the top of the table. Clicking on a row will reveal the submission and allow you to edit the data.
{% endhint %}

### **Export Options**

* **Export All** – download the full set of submissions as an Excel file.
* **Filter-aware exporting** – if filters are applied, only the filtered results will be included in the export.

### Deleting a Form Submission

To delete a form entry, tick the box next to the team name and click **Remove**.

This action will:

* Permanently delete the submission.
* Unlock the form for the associated team, allowing them to submit a new entry.

{% hint style="success" %}
If you need to **unlock a form** for a team, simply delete their existing submission and they will be able to resubmit.
{% 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 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.eventflowapp.com/eventflow-cms/eventflow-reports/form-reports/form-submission.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.