> For the complete documentation index, see [llms.txt](https://docs.frase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frase.io/feature-reference/agency-client-portal.md).

# Agency Client Portal

The Client Portal is a formal approval workflow for your end clients before content gets published. You share a document, your client reviews it in the portal, they approve it or ask for changes, and you get things ready to ship without leaving Frase.

<figure><img src="/files/rs6p7WeI16kqTZjVEHCn" alt=""><figcaption></figcaption></figure>

This is different than adding an *External Collaborator* to a document, and the Client Portal is designed for agencies to make communication between all parties a breeze.

Here's the quick distinction:

| <p><br></p>      | **External Collaborators**                                 | **Client Portal**                               |
| ---------------- | ---------------------------------------------------------- | ----------------------------------------------- |
| **Best for**     | Ad-hoc sharing with freelancers, partners, or stakeholders | Formal client sign-off before publishing        |
| **Scope**        | Per-project or per-folder                                  | Organization-wide (one portal per org)          |
| **Permissions**  | Granular—view, comment, suggest, approve, edit             | Review and approve shared content               |
| **Branding**     | Frase-branded share links                                  | White-labeled with your own branding and domain |
| **Availability** | All plans                                                  | Enterprise plan                                 |

Reach for **External Collaborators** when you want to loop someone in quickly, and the **Client Portal** when you want a polished, branded approval experience for a client.

{% hint style="info" %}
The Client Portal is an **Enterprise** feature. There's one portal per organization, and you'll use that same portal across all of your clients—each client only sees the content you've shared with them, not work shared with anyone else.
{% endhint %}

### How the workflow works

Throughout the workflow, each document carries a status so you always know what's waiting on the client and what's cleared.

<figure><img src="/files/udFcPJtXT9JLtZj8QCgB" alt=""><figcaption></figcaption></figure>

Here's the flow:

1. From your content, **share the document with your client** to send it to the portal for review.
2. **Your client receives an email** with a link to the portal and opens it from there.
3. In the portal, **your client reviews the content** and either approves it, requests changes, or leaves comments on specific sections.&#x20;
4. You see their approval status and comments back in the main Frase app alongside the original document, make any revisions, and send it back for re-review.
5. Once the client approves, the content is signed off and ready to publish.

<figure><img src="/files/f33YdFqjqV5XwjZPM3gR" alt=""><figcaption></figcaption></figure>

### Set up the portal&#x20;

Setup happens in your settings, where you turn the portal on and apply your branding so the experience looks like yours, not Frase's:

1. Head to **Settings** > **Client Portal**.&#x20;
2. Toggle the *Portal Status* on.
3. Add your *Branding*—your portal name, logo, and brand colors—so the portal matches your agency's look.
4. Adjust your Features settings—setting the scope and permissions around comments, approvals, and publishing between the client and your team.
5. Add clients and share the specific content you want each one to review.

{% hint style="info" %}
**Need white-labeling?** By default, the client portal links to a Frase URL. To request a custom domain, reach out to <support@frase.io> with the domain you'd like to use.&#x20;
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.frase.io/feature-reference/agency-client-portal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.