> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/workspace/sharing-and-collaboration/share-a-report-by-link.md).
# Share a report to the Web
Whaly offers 2 ways of sharing a report:
1. Sharing Link
2. Public Link (deprecated)
## Sharing Link
A Sharing Link is a link that can be accessed by anyone even those not having a Whaly account. It's perfect for partners, investors, TV in your offices, etc.
A Sharing Link can:
* 🔐 Be password protected to make sure your data is secured
* 🔎 Contains a set of pre-defined filters to restrict access
A single report can have multiple Sharing Link with different passwords and pre-defined filters for each audience. This way you can share a single dashboard to hundred of different stakeholders.
To create a **Sharing Link**, click on "share" on the top right corner of a Report.
On the panel that open, you can view all the already existing **Sharing Links**, edit them or get their link.
At the bottom of the panel, you can click on "**New Sharing Link**" to create a new sharing link.
## Public Link (⚠️ deprecated)
A Public Link is generating an URL that gives access to the report to all people loading it. A Report can only have a single Public Link.
{% hint style="warning" %}
Public Link were deprecated in February 2022.
You should use a Sharing Link instead as Sharing Link gives you more flexibility and security (filters, password, multiple).
Existing Public Link will continue to work but it'll soon be impossible to generate new ones.
{% endhint %}
### Create a Public Link
* Open a report and in the top right corner, click on "**share**"
2\. Enable the Link Sharing by switching the toggle
3\. Click on "**Get link**"
4\. And Voila! you have the Public Report Link in your clipboard, you can paste it anywhere you need (Slack, Email, [**Whaly Chrome Extension**](/embedding/embed-in-business-apps/google-chrome/configure-the-chrome-extension.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://docs.whaly.io/workspace/sharing-and-collaboration/share-a-report-by-link.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.
