> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-voice-agents/how-to-set-up-your-ai-voice-agent/voice-agent-settings-guide/configure-call-public-call-link.md).

# Configure Call – Public Call Link

Choose whether the recording links of your agent's calls play for anyone who has them, or open the call inside Dapta only after sign-in.

**Public call link** decides who can open the recording of this agent's calls from a link that leaves Dapta: a webhook, a notification email or an export. Turn it on and the link plays for anyone who has it. Turn it off and the link takes people to the call inside Dapta, where they have to sign in first.

You'll find the switch in your voice agent's **Settings**, in the **Call Settings & Behavior** section. As the app puts it: "Anyone with the link can listen to the recording and read the transcript. Turn it off to keep this agent's calls private."

***

### What changes with the switch

|                                                                       | **Public call link** on                                                   | **Public call link** off                                   |
| --------------------------------------------------------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Recording link sent out of Dapta                                      | `https://files.dapta.ai/calls/<file>`, which plays the recording directly | A link to the call inside Dapta, which opens after sign-in |
| The link copied with a call's share button, opened without signing in | Shows the recording and the transcript                                    | Shows the sign-in page                                     |

The switch applies to every recording link that leaves Dapta:

* The `recording_url` field of the post-call webhook.
* The call notification emails, including the ones you resend. See [Post Call Analysis – Notifications](/ai-voice-agents/analyze-your-calls/post-call-analysis-notifications.md).
* The **Recording URL** column when you download call logs. See [Managing your sequence](/ai-voice-agents/how-to-create-your-first-campaign-in-dapta/managing-your-campaign.md).

The storage address where the recording is kept is never sent.

{% hint style="info" %}
**If you read the post-call webhook:** `recording_url` points at `https://files.dapta.ai/calls/…` for an agent with **Public call link** on, and at the call page inside Dapta, which needs sign-in, for an agent with it off. `public_log_url` always points at the call page inside Dapta. The screening recording of an agentic warm transfer, inside the call's transcript, follows the same rule.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/ai-voice-agents/how-to-set-up-your-ai-voice-agent/voice-agent-settings-guide/configure-call-public-call-link.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.