[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)

# Restrict Fathom call share links to people you added

> Find Fathom calls open to anyone with the link and switch them to people only, keeping the ones you mark public. Runs weekly in bulk.

Source: https://cotlet.dev/integrations/fathom-video-api-mcp-server/restrict-share-links

A Fathom recording of a client call can be open to anyone who holds its address, and the setting is chosen call by call. Months later, nobody knows which links are still wide open.

Cotlet does it in your own Fathom account with list\_calls, get\_call\_sharing and set\_link\_access, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Fathom do this on its own?

Fathom has no bulk change for link access and no API for sharing (checked 22 Oct 2026). The API has a read-only shared\_with field showing the team scope of a call, the settings page changes the default for new calls only, and neither the API reference nor the MCP overview lists a way to change link access on an existing call.

## How you do it in Fathom today

1. You open a call and click Share below the meeting title. To the left of Copy Link you pick Anyone with the link can view, Anyone on the same domain as you can view, or Only people added can view.
2. On an Individual or Free plan the link sent to attendees is set to Anyone with the link by default, so you change it for each recording you want to restrict.
3. On a Team plan the Default Share Link Access setting decides new calls. If it says Anyone with the link, attendees can forward the link and anyone holding it can open the recording.
4. To cut one person off, you click Remove next to their email in the sharing details. Fathom has no way to unsend a recording already shared by email.

## How to restrict Fathom call share links to people you added

Prompt

```
List my Fathom calls from the last 30 days that anyone with the link can open. Set them to only people added, except calls with the meeting type Public webinar, and tell me who stays on each.
```

1. 01  
### Find the exposed calls  
The agent lists the window with list\_calls, 30 days unless you say more, and checks each call with get\_call\_sharing. It keeps calls whose link\_access is anyone\_with\_link, because same\_domain and only\_people\_added are already tight.
2. 02  
### Apply your exceptions  
Calls you named as public, for example a meeting type called Public webinar or titles with a prefix, are skipped. The agent states each skipped call and the rule that skipped it, so a public call never gets locked by mistake.
3. 03  
### Read who is on the list  
Before changing a call, it keeps the people list from get\_call\_sharing. Switching to only\_people\_added leaves added people in place, so the report shows who still has access afterwards.
4. 04  
### Switch the link  
set\_link\_access sets only\_people\_added on each remaining call. It waits for your OK by default, because a link a customer relies on stops working for people who were not added.
5. 05  
### Check the result  
The agent reads get\_call\_sharing again for each changed call and reports any call where the setting did not stick, for example one where your role cannot see the sharing details.

### What you get back

Example data

```
Calls in the last 30 days: 41
Open to anyone with the link: 17
Restricted 14, e.g. "Q4 pricing review" (3 people added)
Skipped 2 (meeting type Public webinar)
Not changed 1: "Vendor onboarding sync", sharing details hidden at Limited access
```

### Other ways to ask

- Run on the 1st of every month and restrict last month's calls recorded with external attendees.
- Only report calls open to anyone with the link, with who is added, and change nothing.
- Set same\_domain, not only people added, for calls recorded by my team this quarter.

## What Fathom allows, and what to know first

- Fathom's three link choices are Anyone with the link can view, Anyone on the same domain as you can view and Only people added can view.
- Fathom documents three access levels for a person on a call: Limited sees transcript, summary and recording, Standard also downloads and sees highlights and action items, and Admin also shares and trims.
- Auto-share sends the summary or recording to every attendee on the calendar invite, including people who did not attend, so the link reaches them before you act.
- On a Team plan, a call set to Anyone with the link stays open to everyone holding it, including people attendees forward it to.

set\_link\_access asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [Fathom Help: Sharing Call Recordings](https://help.fathom.video/en/articles/295616) · [Fathom Help: How Does Fathom Auto-Share Recordings and Summaries with Attendees?](https://help.fathom.video/en/articles/7574785) · [Fathom Help: Release Notes](https://help.fathom.video/en/articles/6220097) · [Fathom Help: Fathom MCP, Connect Claude and ChatGPT](https://help.fathom.video/en/articles/11497793)

## Call set\_link\_access from a script

curl

```
curl -X PUT https://cotlet.dev/api/v1/fathom-video/calls/610313346/link-access \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"link_access":"only_people_added"}'
```

Example response

```
{
"call_id": "610313346",
"link_access": "only_people_added",
"previous": "anyone_with_link"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is fathom\_video\_write → set\_link\_access. Example data.

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

## Fathom tools this automation uses

__Cotlet Fathom tools used to restrict Fathom call share links to people you added__
| Tool | Parameters |
| ------------------ | ------------------------------------------------------------- |
| list\_calls | scope, created\_after, created\_before, meeting\_type, cursor |
| get\_call\_sharing | call\_id |
| set\_link\_access | call\_id, link\_access |

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

## Frequently asked questions

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

Yes. You sign in to Fathom yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Fathom 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 Fathom automations

- [Mark Fathom action items done and keep them current](https://cotlet.dev/integrations/fathom-video-api-mcp-server/update-action-items.md)
- [Rewrite Fathom call summaries for the client](https://cotlet.dev/integrations/fathom-video-api-mcp-server/rewrite-call-summaries.md)
- [Fathom API and MCP server: every tool](https://cotlet.dev/integrations/fathom-video-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Fathom.

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

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

---

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.