> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/design-collaboration/survey-link-and-screenshots.md).

# Survey link & screenshots

The **Survey Link** shows the scripted survey on the Design page, as respondents will see it. Use it to check the survey before you approve it for fielding. When you see a problem, take a screenshot and add a comment to it.

![The Survey Link with the scripted survey on the left and screenshot comments on the right](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2F2OWXrGAjeBngbD8xo9wN%2F28-survey-link.png?alt=media)

## Open the Survey Link

1. Open the project and select **Design** from the left sidebar.
2. Select **Survey Link**, next to **Setup** and **Draft**.

The Survey Link is available after the SP syncs the survey to Decipher. A label at the top shows which version you see, for example **Showing V2 · scripted**.

Use these controls above the survey:

| Control                  | What it does                                                |
| ------------------------ | ----------------------------------------------------------- |
| Desktop and mobile icons | Show the survey as it looks on a computer or on a phone.    |
| **Screenshot page**      | Takes a screenshot of the page that you see, for a comment. |
| Reload icon              | Starts the survey again.                                    |
| Open icon                | Opens the survey in a new browser tab.                      |

## Add a comment with a screenshot

1. Go to the survey page that has the problem.
2. Select **Screenshot page**.
3. In the **Survey feedback** box in the **Comments** tab, select the question, or select **Survey feedback (general)**.
4. Describe the problem, then post the comment.

The comment shows in the **Comments** tab with **Screenshot attached**. Your team sees it on the Design page.

## What your client sees

If you share the Survey link with your client, your client sees a **Survey Link** tab in their review link. A client with the **Comment** or **Edit** access level can also take screenshots and add comments. Their comments show in your **Comments** tab, with the other client comments. For more information, refer to [Setting up client access](/design-collaboration/setting-up-client-access.md).

{% hint style="info" %}
Survey Link comments stay on the Design page. They do not show in the Programming workspace. To get a fix into the survey, change the questionnaire and hand off a new version, or tell the SP directly.
{% endhint %}

Next, [hand off a new version during scripting](/design-collaboration/handing-off-a-new-version-during-scripting.md).


---

# 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://help.metaforms.ai/design-collaboration/survey-link-and-screenshots.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.