> 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/edit-form-settings.md). # Edit Form Settings Edit Form Settings lets you edit the settings of a form. ### Editing Form Settings in Eventflow When you're on an existing form’s settings page. {% @guideflow/guideflow-embed requestedUrl="" %} #### Basic Info * Title – Update the name of the form to better reflect its purpose. * Description (optional) – Modify or add internal notes. This is for your team’s reference and won’t appear on the front end. #### Submission Rules Is editable – choose whether users can make changes to their submission after it's been sent. #### Visibility & Publishing Is published – toggle this setting to control whether the form is live or still draft. Set to 'No' if you're not ready for users to see or complete the form. #### Guest access and task completion Enable **Is a guest form?** to let people complete the form without signing in. You can share the public link with staff, contractors or other people who don’t have an Eventflow account. {% hint style="info" %} When **Is a guest form?** is enabled, a public link appears in the Manage Forms table. You can copy and share this link. {% endhint %} Responses submitted through this link appear as **Guest submission** in Form Reports. They aren’t linked to an exhibitor’s team and don’t mark that team’s task as complete. Adding name or company fields helps you identify respondents, but doesn’t create that link. **Opening the public guest link still creates a guest response, even if you’re already signed in.** To record team task completion, open the form through its linked task in the manual. If exhibitors need to complete the form as a task, link it using the **Form** task type and ask them to submit through their accounts. To collect additional responses from staff or contractors, share the guest link at the end of the form or in its confirmation message or email. Keep it out of the task description so exhibitors follow the account-based process first. --- # 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.eventflowapp.com/eventflow-cms/forms-settings/edit-form-settings.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.