> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/forms-overview/create-form.md). # How to Create a Form ### Before you begin (Prerequisites) * **Permissions**: You must be an **Administrator**, **Supervisor**, **Manager**, **Support**, or **Account Rep**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **Form Plan**: Know what information you need to collect and which audience the form targets (members, guests, or prospects). ### Instructions #### 1. Create the Form 1. Navigate to [**ENGAGE > Survey & Forms > Manage Forms**](https://control.peoplevine.com/surveys). 2. Click **Add a Form** (top-right). 3. Enter the **Form Name** (required). 4. Optionally enter **Form Details** using the rich text editor — this text displays to the user at the top of the form. 5. You can click **CREATE FORM** now to create a basic form, or continue to configure the advanced settings below before creating. #### 2. Configure Advanced Options (Optional) Under **Advanced Options**, toggle on any of the following as needed: * **Attach this form to another experience (disable standalone form)** — links this form to an out-of-the-box experience. When enabled, select an experience (e.g., Contact Us Page, Guest Pass, Nominate a Member, and others). See: [How to Attach a Form to Another Experience](/products/control-panel-overview/forms-overview/attach-form-to-portal.md). * **Pre-fill questions they have already answered on another form** — auto-populates answers from previous form submissions. This option is hidden when **Edit Enabled** is selected as the response mode, since pre-fill is always applied when editing is enabled. * **Enable Kiosk Mode — we will automatically clear personal info upon submission** — after each submission, the form clears the previous person's details so the next person starts with a blank form. Turn this on when the form is completed by more than one person on the same device — for example a front desk, a kiosk, or a shared computer or phone. Without it, consecutive submissions on the same device can be saved onto the previous person's CRM profile. * **Create a profile for someone else** — creates a separate CRM profile using the submitted information. **Email and mobile number must be unique.** Best used for a spouse, guest, or family member applying through the form. #### 3. Set Response Options Under **Response Options**, select one: | Option | Behavior | When to use | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | **One Response** | Users are limited to one response. Editing is disabled | Applications where you want a single, locked submission per user | | **Multiple Responses** | Users are allowed to submit multiple responses to the same form. See: [How to Enable Multiple Responses on a Form](/products/control-panel-overview/forms-overview/allow-multiple-submissions.md) | Waitlist forms where the same user may submit multiple entries | | **Edit Enabled** | Users can edit their form as often as desired | Applications where you want users to be able to come back and update their answers | Optionally, customize the **Submit** button text (e.g., "Complete", "Submit Responses"). #### 4. Set Permissions & Owner * **Who can view and complete this form?** — select the audience from the dropdown (e.g., Anyone (Public), members only, specific groups). * **Select Owner Profile** — optionally assign a directory profile owner for this form. #### 5. Configure Confirmation Page * **Confirmation Header** — the heading shown after submission (default: "Thank You"). * **Confirmation Text** — the message shown after submission (default: "Thank you for taking the time to fill out this form"). #### 6. Set Notifications * **Notify Me** — leave unchecked. Instead, configure notifications separately so you can control the triggers and recipients. See: [How to Set Up Alerts and Notifications](/products/control-panel-overview/admin-overview/manage-alerts.md). #### 7. Save and Add Questions 1. Click **CONTINUE** to save the form and proceed to the question builder. 2. Enter your question text in the **Type Your Question Here** field. 3. Select a **Question Type**: **Question types:** | Question Type | Use Case | | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | **Short Answer** | Single-line text (name, email, phone) | | **Long Answer** | Multi-line text (comments, notes) | | **Dropdown** | Dropdown — one selection from a list | | **Select One (Radio)** | Radio buttons — one selection from visible options | | **Select Multiple (Checkbox)** | Checkboxes — multiple selections | | **Opt in Email** | Yes/No marketing email consent. Yes = opted-in, No = opted-out. Auto-maps to the email consent field on the CRM record (no manual mapping needed). | | **Opt in SMS** | Yes/No marketing SMS consent. Yes = opted-in, No = opted-out. Auto-maps to the SMS consent field on the CRM record (no manual mapping needed). | | **Pick a Date** | Date picker (e.g., date of birth) | | **Rating (1 - 5)** | 5-point rating scale | | **Rating (1 - 10)** | 10-point rating scale | | **Yes or No** | Boolean toggle | | **Attach a File** | File upload (e.g., photo, document) | | **Signature Line/Canvas** | Signature capture (e.g., waivers, agreements) | | **Capture Any Payment Method**\* | Collect payment method details | | **Capture Credit Card**\* | Collect credit card details specifically | | **Capture Bank Transfer/Direct Debit**\* | Collect bank/ACH details | | **Capture Address** | Collect a full address | \*Requires a **Stripe** or **GoCardless** integration. A **"Use For"** selector allows you to specify the payment purpose — **Default Payment Method**, **Membership Dues**, **Dining / Shopping**, or **Save To Account**. > **Option-based questions** (Dropdown, Select One, Select Multiple): enter the choices in **List the Options** (one per line). **Pre-fill options from a dynamic list**: instead of typing choices, an option-based question can pull its options from a built-in source. Under **Pre-fill Options with Dynamic Data**, choose one: | Source | Populates the list with | | ----------------------- | --------------------------------------------------------- | | **Countries** | The full international list of countries. | | **States** | U.S. states. | | **Upcoming Events** | Your account's approved, upcoming events — soonest first. | | **Membership Programs** | Your membership programs. | | **Directory Profiles** | Your directory profiles. | | **Business Locations** | Your business locations. | | **Genders** | A standard list of gender options. | ![Form question type chooser showing Opt in Email and Opt in SMS](/files/V2Pv0Pv9R7PECNr1meGN) > **Recommended wording for opt-in questions:** > > * Email Opt-In: "I agree to receive emails from \[Company Name]." > * SMS Opt-In: "I agree to receive SMS messages from \[Company Name]." > **Note**: When a form does not include any opt-in/opt-out questions, the company-level CRM default applies to new records. See the **CRM** section in [How to Configure Company Settings](/products/control-panel-overview/admin-overview/configure-company-settings.md). > **Note**: On the Member Portal, opt-in questions default to **No** (not opted in). If the person already has an opt-in preference saved on their CRM record, the form respects the existing preference rather than overriding it. **Layout & utility elements:** | Element | Use Case | | -------------------------------- | -------------------------------------------------------------------------- | | **Hidden Field** | Invisible field for passing data (e.g., tracking parameters or attributes) | | **Display Text/HTML** | Display static text or HTML content on the form | | **Section Divider** | Visual separator between form sections | | **Request Password (Encrypted)** | Secure password entry field | | **Encrypted Data** | Encrypted data capture field | 4. Optionally add **Additional Instructions** for the question. 5. Toggle **This field is required** for mandatory fields. 6. Optionally set a **Custom Field Name**. If used, field names must be unique — duplicate names will cause errors on submission. 7. Under **Map Response to User's Profile**, select a CRM field mapping if you want the answer to write directly to the user's CRM profile (e.g., first name, email, birthdate). Default: No Mapping. See: [How to Map Form Fields to CRM Profile or Attribute Group](/products/control-panel-overview/forms-overview/map-form-fields.md). When the answer is mapped to **Birthday**, you can set a minimum age based on the submitted date of birth. Toggle **This field is required** on first — it must be enabled before you can turn on the **Set minimum age requirement** option. 8. Under **Customize Field**, set the field width (Full Width, 1/2, 1/3, 1/4, 2/3, 3/4, or Break into 3 Columns) or add a custom CSS class. This controls the form page layout — half-page questions should be paired with another half-page question to complete a line. 9. Click **ASSIGN QUESTION** to add this question and create another, or **ASSIGN & FINISHED** to add this question and finish. #### 8. Create a Vanity URL (Optional) You can give the form a branded vanity URL (e.g., `yourdomain.com/feedback`). See: [How to Create a Vanity URL](/products/control-panel-overview/admin-overview/create-vanity-url.md). ### Best Practice For any member form, include first name, last name, and email fields and use **Map Response to User's Profile** to ensure responses map to the correct CRM profile. See: [How to Map Form Fields to CRM Profile or Attribute Group](/products/control-panel-overview/forms-overview/map-form-fields.md). When a form is completed by more than one person on the same device (for example a front desk, a kiosk, or a shared computer or phone), turn on **Enable Kiosk Mode** (Advanced Options) so each submission clears the previous person's details. This prevents separate people's responses from being saved onto — and merged into — the first person's CRM profile. ### What Happens Next * **On the system side**: The form is live. To find the direct link, navigate to [**ENGAGE > Survey & Forms > Manage Forms**](https://control.peoplevine.com/surveys), click on the form, and look for the **Link to the form** in the **Launch Form** panel on the right. Submissions appear on the Form Detail page under **RECENT RESPONSES**. See: [How to Manage and Export Form Responses](/products/control-panel-overview/forms-overview/manage-form-responses.md). *Last updated: 2026-06-24* --- # 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://help.peoplevine.com/products/control-panel-overview/forms-overview/create-form.md?ask=&goal= ``` `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.