Set up protection with confidence.

A server owner or administrator can add Sentinel through Discord’s installation screen. Choose the correct server, review the requested permissions, and complete authorisation.

1. Open the installer. Use the button below or the installation link on the home page.
2. Select a server. Discord only lists servers where you can add applications.
3. Review access. Sentinel needs message and moderation permissions only for the actions you enable.
4. Open the dashboard. Sign in separately so Sentinel can show servers you own or manage.

Discord evaluates permissions per channel and by role hierarchy. A server-level permission can still be blocked by a channel override.

Run /sentinel setup for a private, guided setup inside Discord. Sentinel can use existing channels or create a named honeypot and a private sentinel-logs channel after you review and confirm every choice.

1. Choose or create the honeypot channel.
2. Leave the action on Observe and report only for the first test.
3. Choose a separate staff-only incident channel or let Sentinel create one.
4. Review the complete configuration.
5. Confirm. Only then will Sentinel create channels, save protection, and publish its warning.

After setup, use /sentinel settings to view or change the shared action and incident destination. Use /sentinel honeypot add, create, remove and list to manage channels. Adding channels preserves settings and safe testers. Rerunning setup shows the existing configuration.

You can also configure existing channels from Your servers. The free open-beta plan supports one honeypot. Clearing the dashboard selection disables honeypot protection without removing Sentinel.

A honeypot is a channel legitimate members have no reason to use. Automated spam accounts often post across every visible channel, so touching the trap provides a high-confidence signal without interpreting normal conversation.

Use a restricted name an automated account might encounter, while clearly warning real members not to interact. Examples include #restricted-access, #system-reserved, or #do-not-post.

• Keep the channel visible but clearly restricted for ordinary members.
• Do not use it for real announcements, verification, or staff conversation.
• Keep incident reports in a different, staff-only channel.
• Do not remove or contradict Sentinel’s persistent warning.

If Discord blocks part of an action, Sentinel reports whether it succeeded, partially completed, or failed. A failed automatic unban is reported as partial so moderators know the member remains banned.

1. Open the server dashboard and add your test account's Discord user ID under Individual safe testers, or select a trusted safe tester role and confirm the bypass warning.
2. Post a harmless message in the honeypot from that account.
3. Confirm the staff report is labelled as a safe test and shows that no enforcement was attempted.
4. Remove the account from the safe list only when you deliberately want to test real enforcement.

Safe testers can include server administrators, who Sentinel otherwise ignores. Their test incidents are retained under the same 30-day policy but are not included in public threat totals.

During open beta, Sentinel sends an immediate report for every trigger. It identifies the member and channel in Discord, configured response, actual outcome, a safe failure code when relevant, and an incident ID.

Noise controls

Weekly aggregate summaries, dashboard-only reporting, and immediate-plus-weekly reporting are planned as free usability choices. A weekly summary will contain totals and outcomes, not a delayed list of named incidents.

The dashboard lists only servers Discord says you own or can manage. For each installed server you can select the honeypot, enforcement action, and incident-report channel.

Protection status

Whether a honeypot is configured and which action is active.

Channel limit

How many honeypots the current entitlement allows.

Installation required

You can manage the server, but Sentinel is not installed there.

Recent incident history will appear here after its authorised API endpoint is ready.

A server owner, administrator, or member with Manage Server can privately redeem a Sentinel premium code with /sentinel premium redeem. Regular members cannot activate a server-wide entitlement.

• Codes have a fixed premium duration, redemption deadline, and total usage cap.
• The same code can never be redeemed more than once for the same server, even by a different administrator later.
• Codes cannot be stacked while premium is already active.
• Use /sentinel premium status to see the current tier, source, expiry date, and remaining validity.

Sentinel stores only what is required to explain and operate protection:

• Guild and channel identifiers.
• A keyed pseudonymous subject reference instead of a recoverable Discord user ID.
• Configured action, actual outcome, safe failure code, reason, incident ID, and timestamp.
• No message body, attachment, Discord OAuth token, or email address.

Raw incidents are automatically deleted after 30 days. Cleanup runs at startup and every 24 hours.