# Permissions & Security

<figure><img src="https://4030380350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNIunBMwyjtHqJK9LyugH%2Fuploads%2FrCC6AmMLQll0XfoFCpNV%2Fpermissions-banner-gradient.svg?alt=media&#x26;token=3c408926-3b8c-4496-af11-84ca31c39bda" alt=""><figcaption></figcaption></figure>

When adding **Sense** to your server you will be asked to authorize the following permissions:\
\
**Manage Channels**\
Sense requires this permission in order to create the 4 necessary channels (see the next section). \
\
**Read Messages**\
Sense needs to read your messages in order to broadcast them! \
\
**Send Messages**\
Sense needs to be able to send messages to populate the channels and keep logging records in the `🪵┃sense-logs` channel. \
\
**Embed Links**\
Required in order to embed the Lite & Pro subscription links, and all other embeds like the `🔔┃get-alerts` embed.\
\
**Read Message History**\
Again, Sense needs to read your messages in order to broadcast them! This is also a permission for future features where we can produce more robust stats for you on your broadcasted messages sent.<br>

{% hint style="success" %}
Many Discord bots ask for a slew of dangerous permissions in your server. This opens them up to security risks in more ways than one.&#x20;

**Sense does NOT request Administrator or Role permissions**, and only uses permissions that are absolutely necessary.
{% endhint %}

{% hint style="danger" %}
**Note: All of these permissions are required for Sense to function.** \
Manually disabling any of these permissions will result in errors or unseen messages.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sensebot.xyz/permissions-and-security.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.