> 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/review-collaboration/setting-up-client-access-pm.md).

# Setting up client access

Found on the project dashboard's **Client Access** tab — where you generate and configure the link you'll send to the client.

![The Client Access tab — review link with Copy and Regenerate, access mode, access level, visibility toggles, and inviting a client](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FJAJQ53WocvPaljNGjyDA%2Fpm-client-access.gif?alt=media)

**Client review link.** A unique URL is generated per project, with **Copy** and **Regenerate** controls.

**Access mode — who can use the link.** *Anyone with this link can access* needs no invitation. *Only invited clients can access* requires an explicit invitation.

**Access level — what they can do.**

| Access level | Client can…                                                                                                                                                                         | The live survey                                                                                |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| View         | Read the questionnaire and the live survey preview. Comment on anything — new comments and replies — and browse existing comments, open and resolved.                               | Read-only.                                                                                     |
| Edit         | Everything View offers, plus type directly into the questionnaire (captured automatically as a tracked, attributed edit), post new comments, and reply within threads they started. | Read-only — their edits apply to the questionnaire document, not the final version of the QRE. |

**Visible to clients.**

| Setting                   | What it controls                                                                                        |
| ------------------------- | ------------------------------------------------------------------------------------------------------- |
| Internal comment / change | Visible to your team only. Notes-to-self, internal QA flags, anything not ready to route to the client. |
| Client comment / change   | Visible to both you and the client. Use for anything you want their input on.                           |
| Questionnaire toggle      | Whether the questionnaire document is visible through the client's link.                                |
| Survey link toggle        | Whether the live survey preview is visible through the client's link.                                   |

**Survey link configuration.** When the **Survey link** toggle is on and the survey is synced to Decipher, the **Survey link configuration** panel opens below it. Use it to give the survey link the values that the survey needs to start correctly, for example the participant source, the language, or a respondent ID.

1. Select the **Participant source** and the **Language**, if the panel shows them.
2. Fill in the fields. Fields marked **required** or **unique** must have a value. If a field has an information icon, put the pointer on the icon to read the guidance from the SP.
3. Select **Save configuration**. This button saves only the survey link configuration. The other settings on this tab save immediately.
4. To check the link, select the open icon next to **Configured survey link**.

![The Survey link configuration with the language, a field, and the configured survey link](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FNMHPKG4bAcRNJR2bZftE%2F29-survey-link-config.png?alt=media)

{% hint style="info" %}
The configuration is for the whole project. Your team's Survey Link tabs and the client's review link all use the last saved configuration. The options come from the last successful sync of the survey to Decipher. If the panel shows an error, or asks for a sync, ask the SP to sync the survey. For the SP steps, refer to [Add guidance for survey link fields](/survey-programming-decipher/unified-flow/add-guidance-for-survey-link-fields.md).
{% 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://help.metaforms.ai/review-collaboration/setting-up-client-access-pm.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.