> 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/forms-settings/add-form.md).

# Add Form

### Adding a New Form in Eventflow

To begin creating a new form, click the ‘Add’ button in the top-right corner. This will take you to the ‘Add Form’ page.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/yr4qmxmflp>" %}

#### Form Settings

* Title – Give your form a clear and descriptive title.
* Description (optional) – Add an internal note or context. This won’t be visible to end users.

#### Edit Permissions

Is editable – Allow users to update their responses after submitting the form.

#### Visibility & Publishing

Is published – Toggle whether the form is live or in draft mode. Set to 'No' to while you're still building or reviewing the form.

#### Guest Access

Is a guest form – Enable this to make the form accessible without a password. This is ideal for collecting data from exhibitors or external stakeholders who don’t have an Eventflow login.

{% hint style="info" %}
When ‘Is a guest form’ is set to ‘Yes’, a public shareable URL will appear in the Manage Forms table under the form name. You can send this link directly to guests.
{% 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/forms-settings/add-form.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.