> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/form-settings/progress-completion/respondent-answers-update.md).

# Respondent Answers Update

Respondents can be allowed to change their answers once they have submitted them. The unique code to restore the survey will be generated by the [key provider](/form-management/security/key-provider-concepts.md). In case no key provider has been setup ngSurvey will generate a random unique code. 

Using this code each respondent can restore his answers using the **Restore answers** button on the [footer](/form-management/form-designer/footer-manager.md) of your survey.

![](/files/-MBn2_uoMWxufPFE4zda)

{% hint style="info" %}
If a [key provider](/form-management/security/key-provider-concepts.md) is used that allows automatic restoring of sessions we recommend to hide the **restore answers** button from the [footer](/form-management/form-designer/footer-manager.md) and to set the answers update option not to show the UID at the end of the survey as these are not needed in such a use case.  
{% endhint %}

## 🚀 Enabling Answers Update

![](/files/-MBmz3NZ8ZIuQprPEw95)

* **`No changes allowed`** respondent cannot modify his answers once they have been submitted.
* **`Allowed and UID shown at the end of the survey`** respondent can change his answers after they have been submitted.  The unique code used to restore the answers is shown to the respondent at the end of the survey.
* **`Allowed and UID not shown at the end of the survey`** respondent can change his answers after they have been submitted.  The unique code used to restore the answers is not shown to the respondent at the end of the survey. This is the recommend option if you're using a [key provider](/form-management/security/key-provider-concepts.md) that automatically handle the restore of the respondents answers like [tokens](/form-management/security/security-items/tokens.md), [invitation codes](/form-management/security/security-items/invitation-code.md), [panels](/form-management/security/security-items/panel-security.md).

{% hint style="info" %}
You may [pipe](/form-management/form-designer/piping/text-data-piping.md) the generated restore unique ode in your survey thanks message using following pipe tag **{{changeuid}}**
{% endhint %}


---

# 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://docs.ngsurvey.com/form-management/form-designer/form-settings/progress-completion/respondent-answers-update.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.