> For the complete documentation index, see [llms.txt](https://docs.modmail.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.modmail.dev/usage-guide/permissions.md). # Permissions The modmail bot comes with an advanced permission system that makes it able to choose which individual users or users with certain roles can use modmail specific commands. The permission levels are the following: * Owner \[5] * Administrator \[4] * Moderator \[3] * Supporter \[2] * Regular \[1] You can view each permission level that is required for the specific command inside the help command.
Screenshot of the Logviewer homepage.
## Setting up permissions These permissions can added in two different ways. ### Adding a level to a role or user `?permissions add level [name] [role/user]` Examples: * `?perms add level Regular everyone` * `?perms add level Moderator @mods` * `?perms add level Owner @user` ### Adding a command to a role or user `?permissions add command [name] [role/user]` Examples: * `?perms add command reply @user` * `?perms add command "plugin enabled" @role` * `?perms add command help 984301093849028` ## Override Permission Level In some cases it can be useful to override a command permission level. This can be done like this: `?permissions override ` Examples: * `?perms override reply administrator` * `?perms override "plugin enabled" moderator` ### Bulk Permissions Override Starting in v4.2.2 (check version with `?about`), permissions can be overridden in bulk. To start the process run: \`?permissions override bulk\`\` *** If you need help setting up permissions, feel free to join our [Discord server](https://discord.gg/zmdYe3ZVHG) and DM Modmail. One of our support members will help you. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.modmail.dev/usage-guide/permissions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.