> 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/administration/allow-restrict-or-disable-devolutions-send.md).

# Allow, restrict or disable Devolutions Send

Devolutions Send is enabled by default. Decide who can use it, and how.

Devolutions Send is enabled by default. Decide who can use it, and how.

## Enable or disable

{% tabs %}
{% tab title="Devolutions Cloud" %}
Go to ***Administration*** – ***System settings*** – ***Advanced***. In ***External sharing***, clear ***Allow users to send messages and passwords securely via Devolutions Send***.

From Remote Desktop Manager, the same option is in the workspace settings, ***Advanced*** – ***External sharing***.
{% endtab %}

{% tab title="Devolutions Server" %}
Go to ***Administration*** – ***Server settings*** – ***Features*** and clear ***Allow users to send passwords with Devolutions Send***.

{% hint style="warning" %}
This option is only available when the server’s internet access is enabled.
{% endhint %}
{% endtab %}
{% endtabs %}

When Devolutions Send is disabled, Remote Desktop Manager offers only the in-app message.

## Choose who can send

{% tabs %}
{% tab title="Devolutions Cloud" %}
The ***Allow sending messages*** setting controls Devolutions Send too:

| VALUE                                   | EFFECT                                                                          |
| --------------------------------------- | ------------------------------------------------------------------------------- |
| ***Send messages with attachments***    | Can share entry passwords and files with Devolutions Send                       |
| ***Send messages without attachments*** | Can send messages, but not share entry passwords or files with Devolutions Send |
| ***No messages***                       | Can’t use Devolutions Send                                                      |
| ***Default***                           | Uses the organization’s value, shown in parentheses (per-user setting only)     |

Set the organization’s value in ***Administration*** – ***System settings*** – ***General***. To override it for one person, go to ***Administration*** – ***Users***, edit the user and open the ***Settings*** tab.
{% endtab %}

{% tab title="Devolutions Server" %}
The ***Permission*** field in the ***Secure message*** settings sets whether secure messages can contain attachments. To share an entry’s password, a user also needs the View password permission on that entry.
{% endtab %}

{% tab title="Remote Desktop Manager" %}
Workspace permissions apply: users can only share what they can see. Attachments can only be added by users allowed to send messages with attachments.
{% endtab %}
{% endtabs %}

## Workspaces limited to shareable links

***Send by email*** and ***Send in-app*** need a Devolutions Cloud or Devolutions Server workspace. With any other workspace type, Remote Desktop Manager and PowerShell only create shareable links. This isn’t a setting.

{% hint style="warning" %}
Devolutions Send lets a secret leave your vaults. Combine these permissions with a [mandatory passphrase](https://docs.devolutions.net/send/administration/require-a-passphrase.md) and [monitored logging](https://docs.devolutions.net/send/administration/logging-and-auditing.md).
{% 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.devolutions.net/send/administration/allow-restrict-or-disable-devolutions-send.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.
