[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Share a Plausible dashboard with a client

> Create a password-protected Plausible shared link or invite a client as a guest from one prompt, without the Enterprise Sites API.

Source: https://cotlet.dev/integrations/plausible-api-mcp-server/share-client-dashboard

A client asks to see their numbers, and you have to decide between a link and a login, create it in the right place in the site settings and remember which one you sent last month.

Cotlet does it in your own Plausible account with list\_shared\_links, create\_shared\_link, invite\_guest and list\_site\_people, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=plausible) [All Plausible tools](https://cotlet.dev/integrations/plausible-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Plausible do this on its own?

Plausible's Sites API can create shared links and invite guests, but only on the Enterprise plan (checked 22 Oct 2026). The Stats API cannot change sharing. Plausible's plan guide lists shared links and team members under Growth, so on Starter, Growth and Business you click the sharing in the app.

## How you do it in Plausible today

1. For a link, an admin opens the site settings, goes to Visibility, finds Shared links and clicks Add shared link.
2. The admin names the link, optionally sets a password and optionally limits the link to a site segment, then saves and copies the link.
3. For a login, the admin opens People in the site settings, clicks Invite New Guest, enters the email, picks Guest Viewer or Guest Editor and clicks Invite.
4. The guest has to sign up or log in with the exact invited address and accept within 48 hours.
5. Nothing in Plausible lists both side by side, so the admin checks Visibility and People separately before sending the same client a second link.

## How to share a Plausible dashboard with a client

Prompt

```
Create a password-protected shared link named "Acme monthly" for acme-shop.example, invite nora@client.example as a Guest Viewer, and tell me the link and who is invited.
```

1. 01  
### Look for an existing link  
list\_shared\_links returns the links already on the site by name. If one called "Acme monthly" exists, the agent returns it and creates nothing, because Plausible shows no password later and a second link only adds one more thing to revoke.
2. 02  
### Pick link or guest  
A shared link needs no account for the viewer and does not count toward your team member limit. A guest needs an account and counts toward it. The agent picks the link when your prompt says "link" or "read-only", and the guest when the client should log in or edit settings.
3. 03  
### Create the link  
create\_shared\_link sets the name, the password you gave and the segment if you named one. The password is set only at creation, so the agent reports it back to you in the result and nowhere else. It waits for your OK first, because the link leaves your control once sent.
4. 04  
### Invite the guest  
invite\_guest sends the email with the role you chose. The agent checks that your account is an Owner or Admin first; an Editor cannot invite, and the call fails with a permission error.
5. 05  
### Confirm who has access  
list\_site\_people shows the invitation as pending until the guest accepts it. The agent reports it and flags any pending invitation older than 48 hours as lapsed.

### What you get back

Example data

```
Shared link created: Acme monthly (password set)
https://plausible.io/share/acme-shop.example?auth=k3T9xQ2mVb7Lw0pD
Invited: nora@client.example as Guest Viewer (pending, expires in 48 hours)
Other guests on acme-shop.example: sam@client.example, Guest Editor, accepted
```

### Other ways to ask

- Create a shared link limited to the "Organic only" segment and send me the URL.
- List every shared link and guest on acme-shop.example so I can see who has access.
- Invite team@agency.example as a Guest Editor on all my client sites.
- Turn on the weekly email report for acme-shop.example and add nora@client.example as a recipient.

## What Plausible allows, and what to know first

- Plausible lets you set a shared-link password only when the link is created. It cannot be viewed, changed or removed later, so a lost password means deleting the link and making a new one.
- A shared link can be limited to one site segment. Viewers can add filters on top of it but cannot remove the segment, and personal segments cannot be used.
- People who view a shared link do not count toward the team member limit, but guests do, and so do pending invitations.
- A Guest Viewer sees the dashboard only. A Guest Editor also manages the site settings.
- Only Owners and Admins can invite guests, change roles or remove people.

create\_shared\_link and invite\_guest ask for your OK by default. To run it on a schedule without you, switch confirmation off for those tools in your dashboard.

Sources: [Plausible Docs: Shared links](https://plausible.io/docs/shared-links) · [Plausible Docs: Users and roles](https://plausible.io/docs/users-roles) · [Plausible Docs: Subscription plans](https://plausible.io/docs/subscription-plans) · [Plausible Docs: Sites API](https://plausible.io/docs/sites-api)

## Call create\_shared\_link from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/plausible/shared-links \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site":"acme-shop.example","name":"Acme monthly","password":"river-lamp-42"}'
```

Example response

```
{
"site": "acme-shop.example",
"name": "Acme monthly",
"url": "https://plausible.io/share/acme-shop.example?auth=k3T9xQ2mVb7Lw0pD",
"password_protected": true,
"segment": null
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is plausible\_write → create\_shared\_link. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/plausible-api-mcp-server.md#automations)

## Plausible tools this automation uses

__Cotlet Plausible tools used to share a Plausible dashboard with a client__
| Tool | Parameters |
| -------------------- | ----------------------------- |
| list\_shared\_links | site |
| create\_shared\_link | site, name, password, segment |
| invite\_guest | site, email, role |
| list\_site\_people | site |

[All 14 Plausible tools with descriptions](https://cotlet.dev/integrations/plausible-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Plausible to Cotlet?

Yes. You sign in to Plausible yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Plausible once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Plausible automations

- [Set up a new Plausible site with goals](https://cotlet.dev/integrations/plausible-api-mcp-server/set-up-new-site-goals.md)
- [Get a weekly Plausible traffic report from your agent](https://cotlet.dev/integrations/plausible-api-mcp-server/weekly-traffic-report.md)
- [Plausible API and MCP server: every tool](https://cotlet.dev/integrations/plausible-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Plausible.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Plausible.

[Sign up free](https://cotlet.dev/app/signup?app=plausible)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.