> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/features/run-developer-experience-surveys/managing-surveys.md).

# Managing surveys

You can create, preview, duplicate, close, and delete surveys.

## Creating a survey

[Read more about creating a survey here](/features/run-developer-experience-surveys/creating-a-survey.md).

## Survey actions

Here's what you can do to draft live, unpublished, and published surveys on the [**Surveys**](https://app.swarmia.com/surveys) tab.

You can access the following actions by clicking `...` in the *Actions* column:

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fgit-blob-04ca94b193aec3ec5fdf251b8c0cff66a7455d09%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### **Preview**

Open a popup showing how the respondents saw, see, or will see the survey. You can respond as if you belong to any team, but your submission won't be recorded.

### **Duplicate**

Start creating a new survey based on another one. You can make changes before [launching the new survey](/features/run-developer-experience-surveys/creating-a-survey.md).

### **Close**

Close a live survey for responses and [access the results](/features/run-developer-experience-surveys/viewing-and-sharing-survey-results.md). A closed survey can't be re-opened.

### **Delete**

Permanently delete a survey or draft.

### **Edit survey**

Add new teams to audience, or change the end date.

### View the survey audience

To see the exact people included in the survey audience, click the team avatars in the *Teams* column.

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fgit-blob-e8efea5a2817874b950476281ec8a6c3b7ec39bc%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### View participation by the team

Click the indicator in the *Participation* column to see the response rates in each team. It’s also available for live surveys to help remind the teams that are falling behind others.

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fgit-blob-e71621b88c5114467c5ba10669e981c4ec1954bf%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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://help.swarmia.com/features/run-developer-experience-surveys/managing-surveys.md?ask=<question>&goal=<user_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.