> 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/data-analytics/collaboration.md).
# Analytic Collaboration
Share your dashboard with other colleagues.
## 🔑 Analytic Dashboard Access rights
Analytic dashboards are only visible to the user who creates them and to ngSurvey administrators. However its possible to grant access to any other users of the system and to define what the user can do with the dashboard .
1. Navigate to your project folder where you saved your dashboard
2. Select its access rights
3. Add the users or group to the list of trusted people who can access that dashboard and define which permissions you would like to grant to that user or group.
{% hint style="info" %}
ngSurvey supports a special user called "Everyone". Granting access to that user will grant access to any users of your ngSurvey setup.
{% endhint %}
{% hint style="warning" %}
The owner of the dashboard will be able to define access rights along with any system administrator.
{% 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/data-analytics/collaboration.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.
