> 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/shared-sessions-surveys.md).

# Shared Sessions Surveys

Shared sessions surveys are specialized surveys that will allow multiple respondents to collaborate on the same survey dataset. Using shared surveys you can deploy one single form as a session to multiple respondents and each of the respondent will be get notified and see in real time all changes done by the other respondents on the survey data. 

Here an example of a form that is shared by two different respondents on two different locations.

<figure><img src="https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8fLhS0bmfBRyq0HdUm%2Fuploads%2FUqVjGimN30SaLwwlzoB4%2F1193d0ec-55c1-4ddf-824b-33ef055e66b1.gif?alt=media&amp;token=7009a015-e23c-42e6-9c6f-3500fecd70d3" alt=""><figcaption></figcaption></figure>

In shared sessions surveys there is no submit button or end page as the data collection process is linked to a session and is never ending until the session is live.&#x20;

To prevent concurrent issues while the respondents are editing the survey data any answer being edited by the respondent is locked for all other respondents connected to the session.

{% hint style="danger" %}
To use shared sessions make sure that your firewall allows web socket based communication and if you are using IIS or Azure to enable web sockets on your installation.
{% 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 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/shared-sessions-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.