Getting started with Sentinel

1. Add Sentinel to your server

Use the “Add to Discord” button and choose the server. You need the Manage Server permission there.

Discord shows the permissions Sentinel asks for. Keep them all: Sentinel is read-only and never needs Administrator.

• View Channels, Read Message History: to see the events to record;
• Send Messages, Embed Links: to post logs in your log channels;
• View Audit Log: to show who performed an action;
• Change Nickname: used only by the Brand plan for a custom bot name.

2. Open the dashboard

Sign in with Discord and pick your server. You see every server where you are the owner or have Administrator or Manage Server; other members can get Moderator or Viewer access if an admin links one of their roles.

3. Choose a default log channel

In Overview, choose the channel that receives logs by default. In that channel Sentinel must be able to view the channel, send messages and embed links.

Tip: create a private channel visible only to your staff, for example #sentinel-logs.

4. Turn on the loggers you need

In the Logger tab, loggers are grouped by area: members and moderation, messages, server structure, voice, content, automation and system.

Each logger has two switches: collection stores the event in the history, delivery posts it to Discord. You can keep a full history without flooding your channels.

Every logger can have its own channel, colour, title, role mentions, retention and exceptions for users, roles and channels, plus an “ignore bots” option.

5. Check the history

History lists every recorded event with its delivery state, so you can see at once why a log did not reach Discord. You can filter by event, search by text or by a user or channel ID, and export to JSON.

6. Give access to your team

In Administration, link Discord roles to the Viewer, Moderator or Admin levels. Levels are checked live against the server, so removing a role removes the access.

Delivery states

• SENT Posted to Discord.
• DISABLED Delivery is off for that logger.
• FILTERED Skipped by an exception (ignored user, role or channel, or “ignore bots”).
• NO_DESTINATION The logger has no channel and there is no default log channel.
• CHANNEL_UNAVAILABLE The channel was deleted, or Sentinel cannot see it or write in it.
• PREMIUM_REQUIRED The logger is not included in the server’s plan.
• FAILED Discord rejected the message even after retries.

Need help?

Ask on the support server, including your server ID and the event you are looking at. Bugs and ideas go to GitHub.