# SecurityBot Mod

The **SecurityBot Mod** role grants access to essential moderation tools while limiting sensitive configuration control. This role is ideal for community managers or support staff who need to act quickly against threats without modifying bot-wide settings.

***

### What Moderators Can Do

Users with the Mod role can:

* Execute moderation commands (e.g. kick, ban, flag)
* View and interact with flagged messages
* Use tools like `/flag user [user]`

They **cannot**:

* Change filter settings or bot configuration
* Adjust admin or mod roles
* Access setup or security settings

{% hint style="warning" %}
**Mod commands can take action across all connected servers using SecurityBot.**\
Assign this role only to trusted staff.
{% endhint %}

***

### Set the Mod Role

Use this command to assign a role as your SecurityBot Mod:

```
/settings mod_role [role]
```

**Example:**

```
/settings mod_role role:@Moderators    
```

Only users with this role (or the Admin role) will be able to use SecurityBot’s moderation tools.

***

### Best Practices

* Create a dedicated role for SecurityBot moderators
* Avoid assigning this to general moderators unless necessary
* Regularly review who has this role to maintain a secure environment

***

Looking to learn more about customization? Continue to the [Changing Settings](https://securitybot.gitbook.io/securitybot-knowledge-hub/bot-guide/administering-securitybot/changing-settings) page to adjust filters, logs, and more.