> 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/what-your-client-will-experience.md).

# What your client will experience

Your client opens the review link and signs in with an email link. Then the client sees the live questionnaire. The access level and the switches that you set control what the client can do and see.

## How the client signs in

1. The client opens the review link.
2. The client types an email address and selects **Continue with Email**.
3. Metaforms sends a sign-in email to the client.
4. The client opens the email and selects **Sign in to collaborate**.
5. The client selects **Continue**.

![The sign-in page that your client sees](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FMe6Dx2jLjnojZBqpKC7f%2F10-client-landing-v2.png?alt=media)

The sign-in link in the email expires after 5 minutes, and the client can use it only one time. If the link does not work, the client selects **Request a new link**.

{% hint style="info" %}
The client can see the message **You don't have access to this project**. This message shows when the client is not on the invite list. Invite the client, or change the option. For more information, refer to [Setting up client access](/design-collaboration/setting-up-client-access.md).
{% endhint %}

## The review page

![The review page of a client with the Comment access level](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FbmefIpPiG3oppDl0AEAf%2F13-client-questionnaire-v2.png?alt=media)

The review page has these parts:

* **Access label**: next to the project name. It shows **View only**, **View & Comment**, or **Edit**.
* **Questionnaire** tab: the live questionnaire.
* **Survey Link** tab: shows after the programming of the survey is complete. You and your client can select this tab to see the finished survey before you approve it for fielding.
* **Side panel**: the **Changes** and **Comments** tabs, and the **AI Assistant** and **Suggestions** tabs if you allow them. A client with the **Comment** level can select **Add as comment** on a suggestion to send it to you as a comment.

## What the client can do

| Access level | Read | Comment | Edit | Chat with the AI                     |
| ------------ | ---- | ------- | ---- | ------------------------------------ |
| **View**     | Yes  | No      | No   | No                                   |
| **Comment**  | Yes  | Yes     | No   | No                                   |
| **Edit**     | Yes  | Yes     | Yes  | Only if **Allow AI assistant** is ON |

A client with the **Edit** level can edit only the fields that you did not protect.

## What the client cannot see or do

* **Internal comments**: the client sees only comments that are set to **Client**.
* **Tracked changes**: the client sees them only if **Show tracked changes** is ON.
* **AI suggestions and AI reasoning**: the client sees them only if you set these switches to ON.
* **Earlier versions**: the client sees only the live questionnaire.
* The client cannot download the questionnaire, hand it off to programming, or invite other persons.

Next, [reconcile client feedback](/design-collaboration/reconciling-client-feedback.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/what-your-client-will-experience.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.