> For the complete documentation index, see [llms.txt](https://malix.gitbook.io/administration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://malix.gitbook.io/administration/discord/native/permissions.md).

# Permissions

## <mark style="color:blue;background-color:blue;">@everyone</mark>

An unassignable role bundling the default permissions every members will have access to (see [#stacking](#stacking "mention"))

Of course it is not recommended and dangerous to give privileged permissions for <mark style="color:blue;background-color:blue;">@everyone</mark> (beware of [nukes](/administration/discord/management/safety.md#issues))

{% hint style="info" %}
To have a server compatible with [the "onboarding" feature](https://discord.com/community/community-onboarding), it has to have its "View Channels" permission enabled
{% endhint %}

## Stacking

Roles' enabled permissions stack, meaning that members with multiple roles will have access to the combined enabled permissions of each of their roles

## Overriding

It is not possible for a role to override permissions.\
Because of that, the only way to override an enabled role permission is by channel permissions overriding

## Administrator

> Members with this permission will have every permission and will also bypass all channel specific permissions or restrictions (for example, these members would get access to all private channels)

To think about it, see granting the "administrator" permission the same as granting the vice-ownership of a server\
There are the differences in permissions between the owner and the "administrator" permission:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><h3>Owner</h3></td><td><ul><li>Doesn't require a role to have their permissions</li><li>Cannot leave the server (has to transfer ownership before)</li><li>Can transfer ownership</li><li>Can delete the server</li><li>Can edit any role</li><li>Cannot have its nickname changed by someone else</li><li>Has an <a href="https://support.discord.com/hc/en-us/articles/360000516572-Server-Ownership-The-Crown-Icon">ownership crow icon</a> next to his name in the online members' list (except if there coexists a role with the "administrator" and "display role members separately from online members" permissions enabled)</li><li>Can change the "Require 2FA for moderator actions" setting</li></ul></td></tr><tr><td><h3>"Administrator" permission</h3></td><td><ul><li>Require a role to have their permissions</li><li>Can leave the server</li><li>Cannot transfer ownership</li><li>Cannot delete the server</li><li>Cannot edit the highest role which has the "administrator" permission enabled</li><li>Can have its nickname changed by someone else</li><li>If granted to any role along with the "display role members separately from online members" permission, it disables <a href="https://support.discord.com/hc/en-us/articles/360000516572-Server-Ownership-The-Crown-Icon">the ownership crown icon</a></li><li>Cannot change the "Require 2FA for moderator actions" setting</li></ul></td></tr></tbody></table>

{% hint style="warning" %}
It means that a member that has the "administrator" permission can grant it to another role, up to [<mark style="color:blue;background-color:blue;">@everyone</mark>](#everyone)
{% endhint %}

## Verification

A [security verification system](/administration/discord/management/safety.md#verification)'s verification role is one that is added after passing it

There are two types of verification roles, <mark style="color:green;">verified</mark> and <mark style="color:red;">unverified</mark>\
There are their differences:

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th></tr></thead><tbody><tr><td align="center"><h3><mark style="color:green;">Verified</mark></h3></td><td><ul><li>When the <a href="/administration/discord/management/safety.md#verification">security verification system</a> is inactive (staff afk or bot down), joining members haven't got access to the server (safer)</li><li>Added after verification <mark style="color:green;">success</mark></li><li>Permissions set as <a href="#overrides">role permission</a> (easy) to enable reading or writing permissions</li><li>If you want to restrict the "View Channels" permission for not verified (<a href="#everyone"><mark style="color:blue;background-color:blue;">@everyone</mark></a>), it is incompatible with <a href="https://discord.com/community/community-onboarding">the "onboarding" feature</a> (see <a data-mention href="#everyone">#everyone</a>)</li></ul></td></tr><tr><td align="center"><h3><mark style="color:red;">Unverified</mark></h3></td><td><ul><li>When the <a href="/administration/discord/management/safety.md#verification">security verification system</a> is inactive (staff afk or bot down), joining members have access to the server (less safe)</li><li>Added after verification <mark style="color:red;">failure</mark></li><li>Set as <a href="#overrides">channels permissions override </a>(tedious) to disable reading or writing permissions</li><li>Compatible with <a href="https://discord.com/community/community-onboarding">the "onboarding" feature</a> in any circumstances</li></ul></td></tr></tbody></table>

## Data Preservation

See [Safety](/administration/discord/management/safety.md#solutions)