Configuration

🔐 Permissions

A complete breakdown of every permission Meta requests when invited to your server, and why each one is needed.

Overview

When you invite Meta to your server, it requests a specific set of permissions needed to power all of its features — from logging and moderation to scanning and protection. Below is a full breakdown of each permission.

36
Total Permissions
7
Management
8
Moderation
21
Functionality

Management Permissions

These permissions let Meta access basic server information and perform fundamental operations.

Permission Category Why It's Needed
Manage Server Management Required to see channels and respond to commands. Without this, Meta cannot function.
Manage Roles Management Powers server logging — Meta reads audit logs to detect who performed actions like bans, kicks, and role changes.
Manage Channels Management Needed for lockdown features, creating log channels, and channel-based protection systems.
Manage Nicknames Management Required for server-level configurations like vanity URL protection and server settings management.
Manage Webhooks Management Allows Meta to add reactions to messages for interactive features and confirmations.
Manage Threads Management Allows Meta to add reactions to messages for interactive features and confirmations.

Moderation Permissions

These are required for Meta's core protection and moderation features like anti-alt, anti-grief, and automated actions.

Permission Category Why It's Needed
Ban Members Moderation Needed for anti-alt bans, anti-grief protection, and the /ban command.
Kick Members Moderation Required for Meta Roles system, anti-grief role restoration, and automated role assignments.
Moderate Members Moderation Allows Meta to manage member nicknames for AutoMod nickname filtering and moderation.
Manage Messages Moderation Used for advanced logging features and webhook-based notifications.
Bypass Slowmode Moderation Enables timeout functionality for AutoMod actions and moderation commands.
Moderate Members Moderation Enables timeout functionality for AutoMod actions and moderation commands.
Mute Users in VC Moderation Enables timeout functionality for AutoMod actions and moderation commands.
Deafen Users in VC Moderation Enables timeout functionality for AutoMod actions and moderation commands.
Move Users in VC Moderation Enables timeout functionality for AutoMod actions and moderation commands.

Functionality Permissions

These permissions are needed for Meta to function properly across various features and commands.

Permission Category Why It's Needed
Create Invites Functionality Core requirement — Meta must send messages to respond to commands and deliver logs.
Change Nickname Functionality Required for AutoMod to delete filtered messages and for purge/clean commands.
View Audit Logs Functionality Allows Meta to send rich embeds for logs, inspection results, and scan reports.
View Channel Functionality Enables file attachments for detailed reports and exported data.
Send Messages Functionality Needed to read previous messages for context in moderation and logging.
Send Messages in Thread Functionality Allows Meta to use its custom status emojis and indicators in embeds.
Embed Links Functionality Used for thread-based features and organized logging systems.
Attach Files Functionality Allows Meta to respond and log within threads.
Read Message History Functionality Allows Meta to respond and log within threads.
Add Reactions Functionality Allows Meta to respond and log within threads.
Use External Emojis Functionality Allows Meta to respond and log within threads.
Use External Stickers Functionality Allows Meta to respond and log within threads.
Create Polls Functionality Allows Meta to respond and log within threads.
Pin Messages Functionality Allows Meta to respond and log within threads.
Connect to VC Functionality Allows Meta to respond and log within threads.
Speak in VC Functionality Allows Meta to respond and log within threads.
Priority Speak Functionality Allows Meta to respond and log within threads.
Video Functionality Allows Meta to respond and log within threads.
Use Soundboard Functionality Allows Meta to respond and log within threads.
Use External Sound Functionality Allows Meta to respond and log within threads.
Set VC Status Functionality Allows Meta to respond and log within threads.

Advanced Permission

Permission Category Why It's Needed
Administrator Advanced Included in the invite for convenience but not required by default. See the section below for details.

⚠️

About Administrator Permission

If Meta is not functioning correctly in your server — such as failing to log events, not banning alts, or not detecting dangerous roles — it may be a permissions issue.

In these cases, you can try granting Administrator permission to the Meta bot role. This gives Meta full access to all channels and permissions, bypassing any channel-level overrides that might be blocking it.

However, this is a last-resort solution. We always recommend using the specific permissions listed above and only granting Admin if you've verified that individual permissions aren't resolving the issue.

If you're unsure, please reach out in the support server and the team will help you troubleshoot.

💡

Pro Tip

Make sure Meta's role is placed above the roles it needs to manage in your server's role hierarchy. Discord requires bots to have a higher role position than any role they modify, assign, or remove.

Ready to add Meta to your server?

Use the invite link below — all the right permissions are pre-selected for you.

Invite Meta Bot