Sentry Bot Documentation

# Home

Support Server (opens new window)

Sentry is a moderation bot for Discord. This site documents its features and how to use it most effectively.

# Configuring Sentry

All Sentry configuration must be done from the dashboard (opens new window). For security and convenience purposes, there are no commands directly in Discord that you can use to configure Sentry.

# Permissions and Hierarchy

The only permissions checked by the bot are enforcement of Discord's role hierarchy, and permissions for application commands that you configure in the Sentry dashboard.

Here are the rules for role hierarchy:

  • A member can never target another member whose highest role is higher than or equal to their own highest role
    • A member can therefore never target themselves, as their own highest role is equal to their own highest role
  • The bot will never allow a member to be targeted whose highest role is higher than the Sentry Bot role
    • This is true even if the bot has been assigned another, higher role
    • This means that the bot could theoretically be given the same role as your moderators, but moderators could be made immune to targeting by the bot if you drag the bot's integration role below the moderator role.
  • Role hierarchy rules are not applied to non-moderation commands, for example /info
  • Naturally, the bot cannot perform an action it does not have role permission to take
    • For example, the /ban command won't work if none of the bot's assigned roles have the Ban Members permission
    • Permissions are not required on the member executing the slash command
    • For example, a member with access to the /ban command can use it even if none of their own roles have Ban Members
    • You can control who can use slash commands on the Commands page of the dashboard

# Time Periods

Some Sentry commands require a time period. Time periods are specified in the format 1w2d3h4m5s (which would mean 1 week, 2 days, 3 hours, 4 minutes, 5 seconds).

Time period options may be specified in any order, spaces are ignored, and any missing units will be assumed as 0. For example, 1m 2d means the same as 0w2d0h1m0s.

# User IDs

Every user on Discord has a user ID. This ID is a long number that never changes, even if the user changes their username or discriminator. Sentry includes a user's ID in the bottom of every log message that relates to that user so you can refer back to that user later without having to know their current Discord tag.

Every slash command accepts a user ID in place of a user tag. For example, if you want to unban a user but Discord isn't auto-populating their username in the /ban remove command, you can use their user ID instead:

User ID slash command example

The same is true of all other slash commands that accept a user as an argument.

You can also tag a user by their ID by typing <@user_id> in the Discord chat box. For example, if you wanted to tag a user in your staff channel but Discord won't auto-populate their username, you can type <@821973078112206891>.

You can add an item to copy a user's ID the context menu when you right-click (or tap and hold) on their username by enabling developer mode in your Discord settings > Advanced.

Settings →