> 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/publish-deactivate-application.md).

# How to Publish or Deactivate an 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).
* **Application Form**: An application must already exist. See: [How to Set Up a Membership Application Form](/products/control-panel-overview/applications-overview/setup-application-form.md).
* **Review**: Verify all form pages, questions, and settings are finalised before publishing.

### Instructions

#### To publish an application

1. Navigate to [**ENGAGE > Survey & Forms > Manage Applications**](https://control.peoplevine.com/survey/groups).
2. Click **Edit** next to the application.
3. Locate the **Survey/Form Status** dropdown.
4. Set the status to **Active**.

> **Note**: The **Survey/Form Status** (Active/Inactive/Draft) controls whether the application is published and accepting responses. This is separate from the application submission statuses (New, Reviewing, Approved, etc.) that track individual applicant progress.

5. Click **Save** or **Update**.
6. Copy the application URL from the **Share** sidebar on the application dashboard to share with prospective members.

#### To deactivate an application

1. Navigate to [**ENGAGE > Survey & Forms > Manage Applications**](https://control.peoplevine.com/survey/groups).
2. Click **Edit** next to the application.
3. Set the **Survey/Form Status** dropdown to **Inactive**.
4. Click **Save** or **Update**.

> **Note**: Deactivating an application does not delete it or remove any submitted data. Deactivated applications are no longer accessible to new applicants. Already-submitted applications continue to be visible in [**ENGAGE > Survey & Forms > View Applicants**](https://control.peoplevine.com/survey/group/0/responses) for processing.

### Best Practice

Before publishing, submit a test application yourself to verify the full flow: splash page, form pages, payment capture, and confirmation page. Deactivate the form only after confirming no applicants are currently mid-submission.

### What Happens Next

* **On the system side**: Active applications accept new submissions via the application URL. Deactivated applications are no longer accessible to applicants. Existing submissions in the pipeline are unaffected.
* **Next step**: Once live submissions come in, review and process them. See: [How to Review Membership Applications](/products/control-panel-overview/applications-overview/review-applications.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/publish-deactivate-application.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.