> 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/setting-up-client-access.md).
# Setting up client access
Send a review link to your client. The client uses the link to review the questionnaire in Metaforms. The client does not need a Metaforms account or a password.
You control three things:
* **Who can open the link**: all persons with the link, or only the clients that you invite.
* **What the client can do**: view, comment, or edit.
* **What the client can see**: for example, tracked changes and AI suggestions.
{% hint style="info" %}
The link always shows the live questionnaire. When you change the questionnaire, your client sees the change immediately. You do not need to send a new link.
{% endhint %}
## Before you begin
* You must have the **Project: Assign Users** permission. If you do not have this permission, speak to your Metaforms admin.
* The questionnaire must have at least one section. The **Share** button does not show for an empty questionnaire.
## Open the sharing settings
1. Open the project.
2. Select **Design** from the left sidebar.
3. Select **Share** in the bar above the questionnaire.
Metaforms opens the **Client Access** tab on the project **Overview** page. Metaforms saves each change on this tab immediately. The only exception is the survey link configuration, which has its own **Save configuration** button.
## Select who can open the link
Under **Client Review Link**, select one of these options:
| Option | Who can open the link |
| ------------------------------------ | -------------------------------------------------------------------------------------- |
| **Anyone with this link can access** | All persons who have the link. You send the link to your client. |
| **Only invited clients can access** | Only the clients that you invite by email. Metaforms sends each client a private link. |
To send the link, select **Copy**. Then paste the link in your email or message to the client.
## Set the access level
Under **Access level**, select one level. The level is applicable to all clients on the project.
| Access level | What the client can do |
| ------------ | ------------------------------------------------------------------------------------- |
| **View** | Read the questionnaire and the client comments. The client cannot comment or edit. |
| **Comment** | Read the questionnaire, and add, reply to, and resolve comments. This is the default. |
| **Edit** | Comment, and change the questionnaire directly. |
When you change the level, the change is applicable to all your clients immediately.
### Protect fields from edits
This option shows only for the **Edit** level. Use it when the client can edit some parts of the questionnaire but not other parts.
Under **Protected fields**, select the fields that the client must not edit:
* **Questions and answer options**
* **Grids**
* **Rationales**
* **Programmer notes**
If you protect one or more fields, the client cannot add or remove questions. You must keep at least one field available for edits. For a review with no edits, use the **Comment** level.
## Set what the client can see
Use these switches to show or hide parts of the questionnaire:
| Switch | What the client sees | Access levels |
| ------------------------ | ------------------------------------------------------------------------------------ | ------------- |
| **Show tracked changes** | The **Changes** tab, the banner for new changes, and the highlights on changed text. | All |
| **Show AI suggestions** | Design flags and the suggested updates to the questionnaire. | Comment, Edit |
| **Show AI reasoning** | The rationales and the thoughts of the AI. | Comment, Edit |
| **Allow AI assistant** | The AI panel. The client can chat with the Design Assistant. | Edit |
{% hint style="warning" %}
**Show tracked changes** is ON by default. To hide your changes from the client, set this switch to OFF before you send the link.
{% endhint %}
**Allow AI assistant** needs **Show AI reasoning**. When you set **Allow AI assistant** to ON, Metaforms also sets **Show AI reasoning** to ON.
## Share the survey link
When the survey is programmed and synced to Decipher, you can also share the survey with your client. Your client then sees a **Survey Link** tab in their review link.
1. Under **Visible to clients**, set **Survey link** to ON. The **Survey link configuration** panel opens.
2. Select the **Participant source** and the **Language**, if the panel shows them.
3. 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 your Survey Programmer (SP).
4. Select **Save configuration**.
5. To check the link, select the open icon next to **Configured survey link**.
{% hint style="info" %}
The configuration is for the whole project. Your team's Survey Link tabs and your 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 your 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 %}
## Invite clients by email
You must invite each client in **Only invited clients can access** mode. In the other mode, invites are optional.
1. Under **People with access**, type the email address of the client.
2. Select **Invite**.
Metaforms sends an email to the client with the subject **You're invited to collaborate**. The email has a sign-in link.
{% hint style="info" %}
The sign-in link in the email expires after 5 minutes. After this time, your client opens the review link and requests a new sign-in email. Tell your client about this when you invite them.
{% endhint %}
The list under **People with access** shows all your clients:
* **Invited**: the client did not open the questionnaire yet.
* **Last active**: the last time that the client opened the questionnaire.
In **Anyone with this link can access** mode, Metaforms adds each client that opens the link to this list.
## Remove access
### Remove one client
1. Under **People with access**, find the client.
2. Select **Revoke**.
{% hint style="warning" %}
In **Anyone with this link can access** mode, a removed client can open the same link again. To stop this, do one of these steps under **Client Review Link**:
* Select **Only invited clients can access**. Then only the clients on your list can open the link.
* Select **Regenerate** to make a new link. Then send the new link to the clients that must keep access.
{% endhint %}
### Make a new link
Make a new link when persons with the old link must not open the questionnaire.
1. Under **Client Review Link**, select **Regenerate**.
2. Select **OK** to confirm.
The old link stops. Copy the new link and send it to the clients that must have access.
## Frequently asked questions
I changed the questionnaire. Do I need to send a new link?
No. The link always shows the live questionnaire. Your client sees each change immediately.
Will my client see my tracked changes?
Yes, if **Show tracked changes** is ON. This switch is ON by default. To hide your changes, set the switch to OFF before you send the link.
Will my client see our internal comments?
No. The client sees only the comments that are set to **Client**. New comments are **Internal** by default.
Can I give different clients different access levels?
No. One access level is applicable to all clients on the project.
Can I set an expiry date on the link?
No. The link stays open until you select **Regenerate** or change to **Only invited clients can access**.
Next, [see what your client will experience](/design-collaboration/what-your-client-will-experience.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/setting-up-client-access.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.