> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/onboarding/claims/external-sharing.md).

# External sharing

Give someone without a Stoïk account, such as your IT provider or a data recovery company, access to the files of a claim through a link. The link expires and can be revoked at any time.

## Prerequisites

* The rights to manage claim files. See [Files](https://docs.stoik.io/onboarding/claims/files.md).

## Create a link

1. In the claim's `Processing` tab, go to the `Data sharing` block and click **Share**.
2. Enter the `Recipient email`.
3. Choose the `Access`:
   * `Download only`: the recipient sees and downloads the files.
   * `Upload only`: the recipient can only send files.
   * `Download and upload`: both.
4. Choose when the link expires, 30 days at most.
5. Click **Create the link**, then **Copy the link** and send it to the recipient.

## Manage shared access

Every link appears in the `Shared access` table of the `Data sharing` block, with its status: `Active`, `Expired` or `Revoked`.

* While a link is active, you can copy it again.
* Click **Revoke** to cut access at once. Only the person who created the link, or Stoïk, can revoke it.
* All links are revoked automatically when the claim is closed.

## What the recipient sees

The recipient opens the link in a browser, with no account needed. Depending on their access, the page shows the claim's files, a zone to drop files, or both, and until when the link is available.

If the link has expired or been revoked, the page says it no longer works. The recipient must ask you for a new one.

{% hint style="warning" %}
Anyone holding the link reaches the files of the claim until it expires or is revoked. Send it only to its recipient.
{% 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.stoik.io/onboarding/claims/external-sharing.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.
