> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/file-storage/details/external-sharing.md).

# External sharing

Links to share files and folders with third parties, with password and expiration date

You can share files or folders with people outside via a link, without giving them an account in the environment.

The concept is in [Access and sharing.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/access-and-sharing.md)

### Shared link options

| Option          | What is it for                                                         |
| --------------- | ---------------------------------------------------------------------- |
| Password        | Making sure having the URL is not enough to open the content           |
| Expiration date | Making sure access closes automatically when the time limit is reached |

### Best practices

* Set **expiration** whenever access is temporary, so you do not leave forgotten live links.
* Add **password** when the content is sensitive, and send it through a channel different from the link.
* Share the **folder** instead of loose files when you need to deliver several documents, and remove the link when it is no longer needed.

> #### 📘 Sharing without opening the environment
>
> The link lets a client or supplier access only what they need, without creating a user account or giving them visibility into the rest. With expiration and password, you share with control and without permanent traces.

### Where to follow

* Who accesses what within the environment: [Permissions](https://docs.plenit.com/docs-en/productos/file-storage/details/permissions.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.plenit.com/docs-en/productos/file-storage/details/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.
