> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/send/how-send-fits.md).

# How Devolutions Send fits across products

One Devolutions Send service, several ways in. What stays the same, and what depends on where you start.

One Devolutions Send service, several ways in. What stays the same, and what depends on where you start.

## One service, several ways in

* **Devolutions apps** (Remote Desktop Manager, Devolutions Cloud, Devolutions Server, Devolutions Password Manager): the main way in. You share content from your vaults, under your organization’s settings.
* **The website** (`send.devolutions.com`): for people without a Devolutions app, usually to share with, or receive from, someone outside your organization.
* **Automation**: PowerShell cmdlets.

## Always the same

* The content is encrypted before it reaches Devolutions Send.
* The link format and the recipient’s experience: every link opens on the Devolutions Send website.
* The two hosting regions, Canada and Europe (France).
* Links expire after a duration and, optionally, a number of views.

## Depends on where you start

|                                  | DEVOLUTIONS APPS                                                                                  | WEBSITE                                                              |
| -------------------------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| Who typically uses it            | Your organization’s users                                                                         | Anyone, often external people                                        |
| What you share                   | Entry fields, attachments, certificates, keys, or a free message                                  | A free message and up to 10 files                                    |
| Request information from someone | No                                                                                                | Yes, with an envelope                                                |
| Durations                        | 1 hour, 24 hours, 3 days, 1 week, 2 weeks, 1 month (30 days) or a custom duration of 1 to 30 days | 1 hour, 24 hours, 3 days, 1 week                                     |
| Send by email or in-app message  | Yes, with Devolutions Cloud or Devolutions Server                                                 | No: shareable links only                                             |
| Rules set by an administrator    | Yes: enable or disable, required passphrase, region, permissions                                  | No                                                                   |
| Logs                             | In the app’s activity logs                                                                        | No activity log; the service only records anonymous usage statistics |
| File size                        | Up to 30 MB                                                                                       | 1 MB without an account, 30 MB with one                              |

For product-by-product details, see [Devolutions Send in Devolutions apps](https://docs.devolutions.net/send/in-app.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.devolutions.net/send/how-send-fits.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.
