> 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/publish-deploy/offline-survey/uploading-respondents.md).

# Uploading respondents

Once you have collected your answers offline you have to upload them back to your server once a connection is available again.

{% hint style="info" %}
In order to upload offline respondents you must first login to upload answers and  the account must have a least access to the survey and Offline respondent upload [rights](/multi-user-management/roles/rights.md)
{% endhint %}

In order to upload offline respondents you must first login to upload answers and  the account must have a least access to the survey and Offline respondent upload [rights](/multi-user-management/roles/rights.md)

You may upload the respondent using either the respondent manager as shown below. 

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MQqrjm-FGqLeCzDcIfc%2F-MQrT1f5FxwslwJeyJVt%2Fimage.png?alt=media\&token=302010dd-c166-425e-aff6-24966c9f2a92)

You may also edit the respondent answers if needed by clicking on the respondent row that you would like to edit 

Or you may also log into ngSurvey's administration interface and within the survey's respondents grid see and manage the offline respondents that have been stored on your browser.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MQrTME_cnSpJHj3SY3i%2F-MQrTxJVtcsWaTpJ0oLy%2Fimage.png?alt=media\&token=4c9b5edb-7cce-4135-9c10-f4aa2c183001)


---

# 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.ngsurvey.com/form-management/publish-deploy/offline-survey/uploading-respondents.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.