> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/surveys/survey-responses/view-responses.md).
# View Responses
On the Results tab, click on the Magnifying Glass (\\) at the front of any row to view that survey response.
On the Results tab, click on the Magnifying Glass (:search:) at the front of any row to view that survey response. (The magnifying glass will not be available for any responses to surveys where confidentiality has been enabled.)
Responses that are still in progress by a respondent will show as Unlocked in the Completed column; the response remains available for the respondent to continue editing for as long as the survey remains open. If for some reason an admin wishes to lock this response from editing, they can do so by clicking on the Lock button at the front of the row in the search results, or in when viewing the response itself. The respondent will no longer be able to edit their response.
Responses that have been submitted by a respondent will show as Locked in the Completed column, and there will be a date and time showing when they submitted their response. If for some reason a respondent needs to revise their response, an admin can enable this by clicking on the unlock button. The respondent will now be able to resume their existing response, make changes as desired, and resubmit when ready.
Admins are able to delete a survey response by clicking on the Trash Can icon (:trash-alt:) at the front of any row.
**Tip:** If you're looking at the admin view of a survey response and want to switch to the respondent view of the same response, just change **/ui/admin/surveys/responses/outline** to **/ui/survey/respond/review** in the URL and press enter. Be sure to leave the "**?session=**" and all the information after it in the URL. Note that unlocked responses
---
# 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.shiftiq.com/help/surveys/survey-responses/view-responses.md?ask=&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.