🔑Permissions

@everyone

An unassignable role bundling the default permissions every members will have access to (see Stacking)

Of course it is not recommended and dangerous to give privileged permissions for @everyone (beware of nukes)

To have a server compatible with the "onboarding" feature, it has to have its "View Channels" permission enabled

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:

Owner

• Doesn't require a role to have their permissions

• Cannot leave the server (has to transfer ownership before)

• Can transfer ownership

• Can delete the server

• Can edit any role

• Cannot have its nickname changed by someone else

• Has an ownership crow icon 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)

• Can change the "Require 2FA for moderator actions" setting

"Administrator" permission

• Require a role to have their permissions

• Can leave the server

• Cannot transfer ownership

• Cannot delete the server

• Cannot edit the highest role which has the "administrator" permission enabled

• Can have its nickname changed by someone else

• If granted to any role along with the "display role members separately from online members" permission, it disables the ownership crown icon

• Cannot change the "Require 2FA for moderator actions" setting

It means that a member that has the "administrator" permission can grant it to another role, up to @everyone

Verification

A security verification system's verification role is one that is added after passing it

There are two types of verification roles, verified and unverified There are their differences:

Verified

• When the security verification system is inactive (staff afk or bot down), joining members haven't got access to the server (safer)

• Added after verification success

• Permissions set as role permission (easy) to enable reading or writing permissions

• If you want to restrict the "View Channels" permission for not verified (@everyone), it is incompatible with the "onboarding" feature (see @everyone)

Unverified

• When the security verification system is inactive (staff afk or bot down), joining members have access to the server (less safe)

• Added after verification failure

• Set as channels permissions override (tedious) to disable reading or writing permissions

• Compatible with the "onboarding" feature in any circumstances

Data Preservation

See Solutions