> 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/survey-programming-decipher/unified-flow/add-guidance-for-survey-link-fields.md).

# Add guidance for survey link fields

Many Decipher surveys need values in the test link, for example the participant source, the language, or a respondent ID. The Research Manager (RM) or Project Manager (PM) enters these values in the **Survey link configuration** when they share the survey with their client. Add a short explanation to each field, so that they know what to enter.

## Before you begin

* The project must be connected to Forsta Decipher. Refer to [Connect Metaforms to Decipher](/survey-programming-decipher/unified-flow/connect-metaforms-to-decipher.md).
* `survey.xml` must have at least one successful sync with Decipher. The fields come from the last successful sync. Changes in the editor that you did not sync do not show.
* You must have permission to edit the survey in Programming.

## Add guidance to the fields

1. Open the project and select **Programming** from the left sidebar.
2. Select **Test survey link**, then select **Sample source field guidance**.
3. Select a sample source from the list on the left.
4. For each field, type what the field is for and what value to enter. You can type up to 240 characters of plain text.
5. Select **Save changes**.

![The Test survey link menu in Programming, with Open test survey and Sample source field guidance](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2Fap21rqtgD8iVdvkgkIuZ%2F30-test-survey-link-menu.png?alt=media)

For example, for a field named `RID`, you can type: *Enter the respondent ID from the panel provider. Use a new ID for each test.*

## Good to know

* Guidance is saved for each field in each sample source. If two sample sources have a field with the same name, add guidance to each one.
* Only fields inside a sample source can have guidance. Global variables cannot.
* To change guidance, open the editor again, change the text, and select **Save changes**. To remove it, delete the text and save.
* After a new sync, the guidance stays on fields that keep the same sample source and the same name. Add new guidance to fields that you add or rename.

## What the RM or PM sees

In **Overview** > **Client Access** > **Survey link configuration**, an information icon shows next to each field that has guidance. When the RM or PM puts the pointer on the icon, they see your text. Fields without guidance have no icon. The guidance is not added to the survey link.

![The guidance for the identifier field shows when the pointer is on its information icon](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FzvYviNdKGCUfW55H5Ymy%2F31-field-guidance-tooltip.png?alt=media)

For the RM and PM steps, refer to Setting up client access in [Design - Collaboration](/design-collaboration/setting-up-client-access.md) or [Review - Collaboration](/review-collaboration/setting-up-client-access-pm.md).

## If the fields do not show

| Message                           | What to do                                                      |
| --------------------------------- | --------------------------------------------------------------- |
| **Decipher integration required** | Connect the project to Forsta Decipher.                         |
| **Sync survey.xml first**         | Sync `survey.xml` with Decipher, then open the editor again.    |
| **No sample-source fields found** | Add variables to a sample source in `survey.xml`, then sync it. |


---

# 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/survey-programming-decipher/unified-flow/add-guidance-for-survey-link-fields.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.