> 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/concepts/access-and-sharing.md).

# Access and sharing

The ways to reach the files (web, local drive, and Remote Desktop) and how to share securely with third parties.

Files are available through several channels at once, depending on how each user works, and they can be shared outward with control.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FyIrLfbwDeND516eVw9cw%2Fdiagram-file-storage-access-paths.png?alt=media&amp;token=f1f9e475-4384-4bb7-a512-a5436014fee3" alt="Diagrama de las tres vías de acceso a Almacenamiento de Archivos: acceso web, unidad en local por SMB y Escritorio Remoto"><figcaption><p>Your files, accessible via the web, as a local drive, or from Remote Desktop: the three channels coexist on the same storage</p></figcaption></figure>

### Access channels

| Channel             | How they access it                             | When it fits                                      |
| ------------------- | ---------------------------------------------- | ------------------------------------------------- |
| Web access          | From the browser, with their credentials       | Mobility, from any device                         |
| Local drive (SMB)   | Mounted on the computer as a network resource  | Work as if on a traditional file server           |
| With Remote Desktop | Integrated into the Remote Desktop environment | When the client already works in that environment |

> #### 📘 They coexist, they don't compete
>
> The same user can have the drive mounted on their laptop and access it via the web from their phone.
>
> You choose the channel for convenience, not because one excludes the other.

### Share with third parties

You can generate **sharing links** files or folders with external people, without giving them a user account. And you do it with control:

* **Password** on the link, so having the URL isn't enough.
* **Expiration date**, so access closes automatically when the period ends.

This way, you share with a client or a supplier without opening your environment or leaving forgotten permanent access.

### Where to continue

* Who accesses what within the environment: [Users, groups, and permissions.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)
* How what is shared is organized: [Folder structure.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/folder-structure.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/concepts/access-and-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.
