> 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/applications-overview/setup-application-form.md). # How to Set Up a Membership Application ### 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 questions and steps to include (personal info, payment, spouse details, references). * **Apply Domain**: Peoplevine's Onboarding Team will set up your application subdomain (e.g., `apply.yourcompany.com`). If this has not been set up yet, contact your Onboarding Team for DNS details to add to your domain provider. ### Instructions #### Part 1: Create the application 1. Navigate to [**ENGAGE > Survey & Forms > Manage Applications**](https://control.peoplevine.com/survey/groups). 2. Click **Setup a New Application**. 3. In the **Application Details** section, fill in the following: | Field | Description | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Application Name** (required) | Name for this application. Displayed at the top of all application pages by default. | | **Application Splash Page** | Rich text editor for introductory content displayed to applicants before they begin the form. See: [How to Set Up an Application Splash Page](/products/control-panel-overview/applications-overview/setup-application-splash-page.md) | | **Confirmation Page** | Select the page applicants see after clicking the final submit button (applicants who abandon mid-way do not see this page). Options: **Default Page** (system "thank you" message) or a custom page you created in ENGAGE > Content > Manage Pages. To build a custom page, see: [How to Create a Confirmation Page](/products/control-panel-overview/applications-overview/setup-confirmation-page.md) | 4. In the **Settings** section, configure the application behavior: | Setting | Description | | ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Include Form Title** | When enabled, the individual form titles for each page in the application flow replace the application name at the top. When disabled, the application name is shown on all pages. | | **Allow applicants to confirm their response before submitting their application** | Toggle on to show a review/confirmation step before final submission. When disabled, the application submits automatically after the last form page | | **Verify applicants haven't already applied and are not a member before continuing through the application** | Toggle on to prompt applicants for their email and/or mobile number upfront. Blocks anyone who has already applied or is already a member. This also prevents a spouse from applying with the primary member's email or mobile number. See: [How to Prevent Previous Applicants from Re-Submitting](/products/control-panel-overview/applications-overview/prevent-application-resubmission.md) | | **Survey / Form Status** | Set to **Active** to make the application available. See: [How to Publish or Deactivate an Application](/products/control-panel-overview/applications-overview/publish-deactivate-application.md) | 5. In the **Permissions** section, optionally set a password to restrict access. See: [How to Set a Password on an Application](/products/control-panel-overview/applications-overview/set-application-audience-permissions.md). 6. Click **Next** to proceed to the form builder. > **Cross-device application resume**: If an applicant pauses partway through, the system recognises returning users (matched on email or phone) and shows a clearer "you already started the application" message with an option to open their email inbox. The resume email contains a secure link that takes the applicant back to where they left off, on any device — desktop, mobile, or tablet. #### Part 2: Add forms to the application flow After clicking Next, the **Survey / Application Flow** page opens. This is where you build the multi-step application by adding forms to the flow. Each form becomes one page of the application. 7. On the **Add Item to the Flow** panel: * **Item Type**: Select **Survey** (default). * **Search**: Type a form name and click **SEARCH** to filter the list. The search box replaces the legacy long radio list of forms. * **Recently used**: The last 10 forms used in any application flow appear at the top of the list for quick selection. * **Form badges**: Each form shows a badge indicating whether it captures a CRM record and/or a payment method, so you can confirm the form's purpose before adding it. * **Select an Item**: Choose an existing form by clicking its radio button. 8. Click **ADD** to add the selected form to the application flow. 9. To add more pages, repeat steps 7–8 for each additional form. 10. To create a new form instead of selecting an existing one, click **SETUP NEW FORM:** — this opens the form builder where you can create a form from scratch. See: [How to Create a Form](/products/control-panel-overview/forms-overview/create-form.md). 11. In the **Modify Existing Items in the Flow** section, configure each page: * **Order**: Set the display order (lower numbers appear first). * **Next Step Text**: Enter the CTA button text shown to applicants to move to the next page (e.g., "You're making good progress! Move to step 2"). * **Remove**: Check to remove a page from the flow. 12. Click **SAVE**. A typical multi-step application follows this structure: | Step | Purpose | Key Fields | | --------------------- | -------------- | -------------------------------------------------------- | | **Step 1** | Personal info | Name, Email, Phone, Address, Date of Birth | | **Step 2** | Payment | Credit Card or ACH fields, Billing Address | | **Step 3** (optional) | Spouse/Partner | Spouse Name, Email, Phone (saves to separate CRM record) | | **Step 4** (optional) | References | Nominator Name, Email, Relationship | > **Tip**: When building form questions, use **controlled inputs** (radio buttons, dropdowns, checkboxes) for fields you want to segment on later, and tag critical fields as **Attributes**. For payment capture, use the question types **Capture Any Payment Method**, **Capture Credit Card**, or **Capture Bank Transfer/Direct Debit**, and set the **Use For** selector to the appropriate purpose (Default Payment Method, Membership Dues, Dining/Shopping, or Save To Account). Payment capture requires a payment processor integration (Stripe and/or GoCardless). Enable **Map Response to User's Profile** on name, email, and phone fields so responses populate the CRM record. #### Part 3: Application dashboard After saving, the application dashboard opens. This page shows stats, applicant tables, and sharing tools. | Area | What It Shows | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | **Header** | Application name, date built, status badge (**Active** / **Inactive**), and action buttons: **Edit**, **Enhance**, **Manage Alerts** | | **Stats** | Applied this Week, Applied this Month, Applied this Year | | **Application Responses** | Table of all submitted applications with Status, Applicant, % Completed, and View link | | **Pending Approval** | Table of applications awaiting a decision | | **Top-right actions** | **View Responses** (all submissions), **Import Data**, **View Flow** (return to the form flow editor) | The **Share** sidebar on the right provides tools to distribute the application: | Tool | Description | | --------------------- | -------------------------------------------------------------------------------------- | | **Preview Your Page** | The icon next to the **SHARE** button — click it to open the application in a new tab | | **Copy URL** | Located next to **Full URL** — click the icon to copy the application link | | **QR Code** | Download a QR code that links to the application | | **Text Messages** | Set up an SMS keyword so applicants can text to receive the application link | | **Promote** | Send the application link via **E-mail**, **Text**, or **Social** using built-in tools | 12. Click **Copy URL** from the Share sidebar and test the application by submitting a test entry before going live. > **Note**: For couples applications, enable the option on Step 3 to save spouse data to a separate CRM record. After approval, manually add the spouse as a sub-member on the membership card. See: [How to Create a Partner/Spouse Profile During Application](/products/control-panel-overview/applications-overview/create-partner-profile-application.md). ### Best Practice * Capture the payment method on Step 2 (the second page), not Step 1. The CRM profile must be created on page 1 first — if payment capture is on the same page, Stripe may attempt to tokenize before the CRM record exists, which leads to an error. * Keep the first form short and capture at least the applicant's email and phone number. The system uses these to recognise returning users early and enable the cross-device resume flow. * If applicants complete the application on a device used by more than one person (for example a front desk, a kiosk, or a shared computer or phone), enable **Kiosk Mode** so each applicant starts with a blank form and their details are not carried over to the next person. Kiosk Mode is a form-level setting — on the form(s) in your application flow, open **Advanced Options** and toggle on **Enable Kiosk Mode**. See: [How to Create a Form](/products/control-panel-overview/forms-overview/create-form.md). * **Set a minimum age to apply**: to require applicants to be a minimum age, add a **Birthday** (date of birth) question to the application form, mark it **required**, then turn on **Set minimum age requirement** on that question. The applicant's entered date of birth is checked against the minimum age. See: [How to Create a Form](/products/control-panel-overview/forms-overview/create-form.md). ### What Happens Next * **On the system side**: The application appears in [**ENGAGE > Survey & Forms > Manage Applications**](https://control.peoplevine.com/survey/groups). Submitted applications appear in [**ENGAGE > Survey & Forms > View Applicants**](https://control.peoplevine.com/survey/group/0/responses) for staff review. * **Next step**: Link this application to a membership program so that prospective members must apply before enrolling — set the **Applicants Must Apply Here** field in the program's Member Signup section. See: [How to Create a Membership Program](/products/control-panel-overview/membership-setup-overview/create-membership-program.md). *Last updated: 2026-05-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/applications-overview/setup-application-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.