👁️ Monitoring

Monitoring is the agent's anti-nuke system. It watches for admin abuse — mass channel or role deletions, ban and kick waves, bulk message purges — and when an admin exceeds the rates you set, the agent acts on that admin automatically before more damage is done.

Overview

When configured, the agent can:

• Track five categories of destructive admin actions against per-admin rate limits
• Respond automatically by stripping the actor's roles, quarantining them, or timing them out
• Alert you when watched roles are granted dangerous permissions
• Post every incident to an alert channel and DM the server owner and other admins
• Take an emergency backup of the server the moment an incident triggers

Configuration

To configure monitoring:

1. Open your project in the Fren One webapp.
2. Select the Discord server you want to configure.
3. In the sidebar under Agent Configuration, select Server Protection, then the Monitoring tab.
4. Toggle "Detect and stop admin abuse" on.

Rate limits

Under "Trigger when an admin exceeds these rates", each of the five limits pairs a count ("Trip after this many.") with a "Within (minutes)" window. When a single admin performs that many actions inside the window, the incident triggers.

Limit	Trips when one admin performs
Channel deletions	This many channel deletions within the window.
Role deletions	This many role deletions within the window.
Member bans	This many bans within the window.
Member kicks	This many kicks within the window.
Bulk message deletions	This many bulk message deletions within the window.

Response

"When triggered" selects what happens to the offending admin:

Option	Description
Strip the actor's roles	Removes the actor's roles, cutting off their permissions. Default.
Quarantine the actor	Assigns the Quarantine role to the actor, stripping their access. Selecting this reveals the required Quarantine role picker.
Time the actor out	Times the actor out. Reveals "Timeout duration (minutes)" — minimum 1, default 60.
Alert only (take no action)	Notifies you but leaves the actor untouched.

Watched roles

"Watched roles" is a role multi-select: the agent alerts you when any of these roles is granted dangerous permissions (admin, manage server/roles). Use it to keep an eye on staff roles that should never quietly gain administrator access.

Notifications

Under "How you are notified of an incident":

Option	Description
Alert channel	Incidents are posted here.
DM the server owner	Sends the server owner a DM for each incident. Default: on.
DM other admins	Also DMs the server's other admins.
Back up the server when an incident triggers	Takes an emergency backup the moment an incident fires. Default: on.

How it works in Discord

The agent tracks destructive actions per admin. When one admin crosses a limit within its window, the agent immediately applies the configured response to that admin — quarantine uses a quarantine role the agent creates, which strips the actor's access while you investigate. An emergency backup of the server is created automatically (when the backup toggle is on), so even if channels or roles were already deleted, you have a snapshot to restore from.

The incident is posted to the alert channel and DMed to the server owner and any other admins you've enabled, and it appears in the Incidents list on the Server Protection Activity tab for later review.

Saving your changes

This page uses a batched save — edits stay local until you select Save in the bar that appears at the bottom of the page. Leaving the page with unsaved changes shows a warning first.

Best practices

Tuning the limits

• Set the counts above your admins' normal cleanup activity — a limit that trips on routine channel reorganization trains people to ignore alerts.
• Keep "Back up the server when an incident triggers" on: the emergency snapshot is what makes recovery possible after a nuke attempt.
• Add every staff role to "Watched roles" so silent permission escalations don't go unnoticed.
• Prefer Quarantine or Strip the actor's roles over Alert only — a nuke can destroy a server in minutes, faster than a human can respond.

Role hierarchy

The agent can only strip roles from or quarantine an admin whose roles sit below the agent's own role in the server's role hierarchy. Keep the Fren One role near the top of the role list, above your staff roles. Actions that fail because of missing permissions or hierarchy are not logged as successes.

Troubleshooting

An incident triggered but nothing happened to the actor?

• Check that the response isn't set to "Alert only (take no action)".
• The actor's highest role may sit above the agent's role — the agent can't act on admins above it in the hierarchy.
• If you've customized the agent's permissions since install, confirm it can still manage roles and time members out.

No incidents are appearing?

• Check the "Detect and stop admin abuse" master toggle.
• The rate limits may be set too high for the activity you expected to catch — each limit only trips when a single admin exceeds the count within its "Within (minutes)" window.

Not getting notified?

• Select an Alert channel and confirm the agent can post in it, or enable the owner/admin DM toggles.

Related features

• 💾 Backups & Restore - Restore channels and roles from the emergency backup an incident creates
• Anti-Raid - Protection from the outside: join floods, rather than abuse by your own admins