> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/access/local-governance-stack/citizen-engagement-module/survey/survey-user-manual.md).

# Survey User Manual

An illustrative guide to using the Survey module

The Survey module allows employees to create surveys for citizens who fill in the details. Later, the survey results are available on the Survey results dashboard.

## Key Features

The Survey module enables employees to create new surveys and share them with citizens for their responses and insights.

Employee user scope of action includes

* Create new surveys
* View surveys
* Edit surveys

Citizen user scope of action includes

* Respond to surveys
* View surveys

## **Using Surveys**

This section guides you through the details of using the Surveys module for each role. Click on the relevant role below to learn more about how to use the Surveys.

* [Citizens](/local-governance/access/local-governance-stack/citizen-engagement-module/survey/survey-user-manual/surveys-citizen-user-manual.md)
* [Employees](/local-governance/access/local-governance-stack/citizen-engagement-module/survey/survey-user-manual/survey-employee-user-manual.md)


---

# 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.digit.org/local-governance/access/local-governance-stack/citizen-engagement-module/survey/survey-user-manual.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.