Explore Archivian's Features

What you get

• Five case types: Note, Warning, Timeout (mute), Kick, and Ban.
• A case is a living record: staff add entries, files, and links to it over time.
• Bans and unmutes are recorded in the original case as tagged entries — no scattered unban/unmute records.
• Timeouts use Discord's native timeout feature, not legacy mute roles.

You control

• Per case type: toggle DM notifications, show/hide the case creator, show/hide the reason.
• Fallback to notifying in-channel when DMs are closed, with an optional custom message.
• Optional educational tips and after-action reports after a case is created.

What you get

• Add multiple entries to a case, each with its own author and timestamp.
• Entries can be tagged, for example as the unban or unmute reason.

What you get

• Files are first-class citizens on cases, hosted by Archivian with no reliance on Discord's CDN.
• Files can be archived (hidden but preserved) and restored with the right permissions.

What you get

• Link Discord users to a case (for example victims or collaborators) with custom labels.
• Link cases to each other bi-directionally, with any label you choose.

What you get

• Make a whole case public, or only specific parts like the files used as proof.
• Visibility rules apply to cases, entries, files, and links independently.
• Users can browse cases made on them in their personal dashboard if you allow it.

What you get

• Archive a case, entry, or file to hide it from normal views.
• With the right permissions, archived records can be viewed or fully restored.

What you get

• Intercepts moderation actions from Discord's built-in tools and other bots.
• Creates cases automatically with whatever information is available (executor, reason, target).

What you get

• Dashboard tool for mass-banning, kicking, or timing out many users at once.

What you get

• Counts, recent activity, and trends across your server's cases.

What you get

• Mark users and optionally add/remove roles while marked.
• Automatically escalate (for example to a ban) if a user is still marked after a set time.

What you get

• Import historical cases from a CSV file when migrating to Archivian.

What you get

• Appeals are part of the platform: users create and follow them from their personal dashboard.
• When notified of a case, users can receive a button that takes them straight to the appeal flow.
• Users can check whether they're banned in a server and appeal retroactively.

You control

• Enable or disable appeals per case type.
• Override the appeal setting on individual cases.

What you get

• A built-in chat between staff and the appealing user, attached to the appeal.
• Can be enabled by default or per appeal.

What you get

• Assigned staff are alerted via dashboard, email, and/or Discord depending on their preferences.
• Assignment automatically grants permission to read and edit the appeal and read the original case.

What you get

• Staff update the appeal status as it moves through your process.
• Users can opt in to alerts when the status changes.

What you get

• Depending on the case type, Archivian executes the reversal for you when an appeal is accepted.

What you get

• Enable file uploads per case type, or override per appeal.

What you get

• Stores message content, full edit history, and deletion records on Archivian's side.
• Old and deleted content is reliably available — not dependent on a cache that resets.
• Detects content removed via edits, not just deleted messages.

You control

• Granular retention policies for message tracking, configurable per channel.

What you get

• Dedicated alerts for deleted files and deleted or edited embeds.

What you get

• Automatically stores file attachments sent in the server for up to 2 weeks.
• Deleted files can be browsed from the dashboard.
• Staff can permanently delete stored files from Archivian's storage when needed.

What you get

• When messages are bulk-deleted (purged), the full set is stored as a collection you can inspect later.

What you get

• Dry-run mode shows the affected messages before deletion.

What you get

• Members vote with reactions; messages crossing the threshold are removed.

You control

• Configure thresholds and where vote-deleting applies.

What you get

• Maintain a server-level blocklist of images that are automatically removed.

What you get

• Reported messages are preserved on Archivian's side — text, files, and embeds — in case of deletion.
• Change history is kept for reported messages.

You control

• Configure how many reports are needed before a report is submitted to staff.

What you get

• Given enough reports, a user report is created in the dashboard for staff review.
• Associated messages from the reported user are tracked for context.

What you get

• Trigger automatic actions when a user or message report crosses a threshold.
• Can delete the reported message or all identical messages sent in the past 48 hours.

You control

• Choose which actions trigger at which thresholds.

What you get

• Reports from users with certain roles count for more, meeting thresholds faster.
• Reports from specific roles (or users without roles) can be ignored outright.

What you get

• Every strike adds points to a member's running total for the server's strike pool.
• An action ladder of rungs fires automatically the moment the total crosses a rung's threshold going up.
• Rungs use hysteresis: once fired, a rung must drop back below its own re-arm score before it can fire again.
• An optional cooldown per rung adds a minimum time between firings on top of hysteresis.

You control

• Configure each rung's threshold, re-arm score, and optional cooldown.
• Build a ladder of up to 25 rungs per pool.

What you get

• Five rung actions are available today: add roles, remove roles, create a moderation case (any case type), send a message (DM or channel), and alert staff for human review.
• Combine multiple actions on a single rung.

You control

• Pick any combination of actions per rung.
• Choose DM or channel delivery for messages, and which case type a rung creates.

What you get

• A strike's points count toward the member's total for its full lifetime, then expire — or fade gradually across it, or never expire at all.

You control

• Set the default lifetime for the whole server, and override it per preset reason.
• Mark a reason as permanent, so strikes given for it never stop counting.

What you get

• Configure up to 20 preset reasons, each with its own point value and lifetime override.
• Severity levels let staff say how bad this particular incident was, overriding what the reason is normally worth.
• The levels can track your action ladder automatically, so they stay meaningful whenever you retune it — or you can set them by hand.

You control

• Add, edit, or remove preset reasons, up to 20 per server.
• Override points and lifetime per preset reason.
• Choose where severity levels come from, or write up to 10 of your own.

What you get

• The /strike command, right-clicking a member, and right-clicking a message all open an in-chat form with a reason picker.

What you get

• /strikes browse and /strikes inspect for reviewing a member's strike history from Discord.
• /strikes pardon keeps the strike on record but removes its points from the member's running total.
• /strikes unpardon reverses that, behind its own permission — deciding a strike was wrong and deciding it was right after all are different calls.

What you get

• Your last rung cannot escalate any further, so without this a member who reaches it is parked above every rung and nothing they do afterwards can trigger anything.
• Reset their score — wipe it, keep a percentage, or drop them to the middle of your ladder — so they have to climb it again.
• Optionally bank permanent points on top, so somebody who tops out twice starts the second climb further along.

You control

• Seven ways to treat their score, with the resulting number worked out against your own top rung as you configure it.
• A cooldown on the permanent penalty, so one incident is not charged twice.

What you get

• Exemptions for specific users, roles, channels, apps, and your staff roster.
• Roles carrying sensitive permissions are protected, so a rung can neither hand one out nor strip one away — on a permission list you control.
• Your registered staff roles are protected too, which catches the role that is powerful only by convention and carries no permissions of its own.

You control

• Tick exactly which permissions put a role out of reach, grouped by what they control.
• Turn either guard on or off independently.

What you get

• Settings, pools, the ladder editor, and sources are all managed from the dashboard.
• The ladder editor shows every pool side by side on one score scale, so you can read what happens at a given score across all of them at once.

What you get

• Each pool has its own sources, its own action ladder, and its own running score on every member.
• Which pool a strike lands in is decided by the source it came from — the reason staff picked, or the Auto-Mod rule that tripped — so the routing is configuration rather than a decision at three in the morning.
• One Auto-Mod rule or check can feed several pools at once, each charging its own points against its own ladder.
• A new pool arrives with its own manual sources, so it can be struck into from the moment it exists.
• Deleting a pool takes its configuration but keeps the strikes: they stay on the member's record as history.

You control

• Two pools on Free, five on Plus, ten on Pro.
• Point each preset reason, Auto-Mod rule and Auto-Mod check at the pool it belongs to, and override it per strike when you need to.
• Set what a manual strike is worth separately in each pool.

What you get

• Each strike loses weight little by little across its lifetime, rather than its full value disappearing in one step.
• You drag the curve's shape, so a strike can hold most of its weight while the behaviour is recent and fall away quickly near the end — or the reverse.

You control

• Choose per pool between fading gradually, counting in full then expiring, and never expiring.
• Drag the two handles on the decay curve to set how the fade runs.

What you get

• Pick the Discord Auto-Mod rules that should cost points — one at a time, not all or nothing. Rules are listed with what kind of rule each is and what Discord already does when it trips, so two rules with the same name are still told apart.
• Pick the Archivian Auto-Mod checks that should cost points the same way: bad links, bad images, server invites, text patterns, cross-posting, and per-member spam.
• A message that trips two checks costs both, because each is a separate rule with its own points and its own pool.
• Rules renamed in Discord keep their source in step. A rule deleted in Discord leaves its source visible and marked, rather than silently discarding the points and lifetime you configured.

You control

• Set each rule's or check's points, lifetime and pool, exactly like a preset reason.
• Point one rule or check at several pools at once, each with its own points and ladder.
• Choose whether re-editing a message that still breaks the same rule costs points again, or whether a message is charged at most once.

What you get

• A strike lands on a person, so a check has to be able to say who is at fault before it can issue one.
• Channel Spam watches a channel filling up regardless of who is posting, so a match is commonly a crowd. It is not offered as a strike source, and the dashboard says why rather than leaving it absent.
• Use the per-member spam check for the same behaviour attributed to one member.

What you get

• Point the ladder at a case type, so opening that kind of case charges points automatically.

What you get

• Configure thresholds that fire on the way down, for example rewarding sustained good behavior.

What you get

• Planned actions: capture/restore roles, delete message, purge messages, voice disconnect/mute/deafen, nickname reset, webhook call, open a ticket, and channel slow mode.

What you get

• Send the struck member a DM when they receive a strike.
• Alert staff automatically when a member crosses a configured threshold.

What you get

• Make strikes count for more on accounts registered recently, or on members who only just joined your server.
• Give a role its own weight, so strikes on the people holding it cost more, less, or nothing at all.
• Every strike shows its own breakdown, so you can see exactly which factor changed the points and by how much.

You control

• Two age curves with their own strength, window, and draggable shape.
• Per-role weights, and a floor and ceiling on the finished multiplier.

What you get

• Members would see their own strikes, points, and lifetimes from their personal dashboard.

What you get

• Build auto-mod modules in a dashboard editor, going beyond what Discord's built-in auto-mod can do.
• Overview dashboard for all your auto-mod systems.

You control

• Custom triggers, thresholds, ignored channels, and actions per module.

What you get

• Violations are recorded and grouped, even when Discord emits multiple events per violation.
• Browse and review historical violations per user and rule.

What you get

• Public template library browsable without even logging in.
• Personal template collections and server-managed templates.
• One-click import into your server's Discord auto-mod.

What you get

• Watches public responses from apps a member installed on their own account, not on your server.
• Scores the member and the app separately, so it catches both one member cycling through many apps and many members hammering one app.
• Points fade on a half-life instead of resetting, so ten uses in a few seconds count very differently from ten spread across an hour.
• Low, Medium, and High levels each open one reviewable incident with the member, the app, the evidence, and staff controls: Clear, Escalate, Punish, Mark hostile, Exempt.
• Actions per level include staff alerts, adding or removing roles, timeouts, letting members vote the messages away, deleting the tracked app output, and kicking or banning the member.
• An app can be marked radioactive so the next member who uses it starts contained — or Archivian can temporarily take Discord's Use External Apps permission away during a severe incident, and hand it back only to the roles it took it from.
• Testing mode observes and alerts without acting, so you can learn your server's normal app usage before anything is enforced.
• Periodic standing summaries list hazardous apps and incidents still in effect, with bulk buttons to defuse them.

You control

• Separate per-level thresholds, actions, alert channels, and pings for member behaviour and app behaviour.
• Heat decay half-lives per side, plus trust discounts for account age, time in the server, trusted roles, app age, and Discord-verified apps — with floors and ceilings so the discounts cannot compound into nothing.
• Exceptions for specific apps, members, roles, and channels; your staff roster is exempt by default.
• Custom messages per level, sent in the channel, as a reply, by DM, or to a channel of your choice.
• Automatic release of an app's level after a set time, or leave app incidents entirely to staff.

What you get

• Save reusable lock presets: pre-made selections of channels and categories to lock and unlock together.
• Two lock modes per preset: read-only (no sending, reactions, voice, or threads) or fully hidden.
• Start or lift a lockdown from the dashboard, or with the /lock and /unlock commands right in Discord.
• Lift a lockdown per channel or for an entire preset — the previous channel permissions are restored exactly as they were.
• Every lockdown and lift is recorded in Archivian's audit logs.
• A built-in debugger explains why a specific user can — or can't — interact with a channel while a lockdown is in effect.

You control

• Build presets targeting any mix of channels and categories, up to your plan's preset quota.
• Choose read-only or hidden mode per preset.
• Permission-gated separately: who can manage presets, and who can start or lift lockdowns.

What you get

• Monitors guild events: channels, roles, webhooks, emojis, stickers, soundboards, and bans.
• Detects destructive patterns against your thresholds and takes configured actions.
• Detailed logs show exactly what triggered — and granular flags explain why an action was not taken.
• Learning (evaluation) mode lets you test your configuration without live consequences.

You control

• Per-trigger thresholds and actions.
• Bypass lists for trusted users, roles, and titles — plus request-based temporary bypasses.

What you get

• Create snapshots of guild state: settings, channels, roles, webhooks, emojis, stickers, soundboards, and bans.
• Roll back the whole server or recover from a nuke using a snapshot.
• A rollback ledger keeps an audit trail of every restore.
• Progress tracking for long-running snapshot and rollback operations.

What you get

• Challenge-based verification with delivery via DM or a public dashboard page.
• Fallback channel method for users with closed DMs.
• Backed by a captcha challenge pool.

You control

• Configurable challenge thresholds and delivery behavior.

What you get

• Trust scoring based on factors such as account age, username originality, and whether the user has an avatar.
• Alerts trigger based on your thresholds, or manually.

You control

• Configure which factors matter and where the alert thresholds sit.

What you get

• Configure automatic triggers, such as creating a case with preset duration and reason.

What you get

• Honeypot roles that trigger automatic actions (like kick or ban) when claimed.

What you get

• Put members under temporary watch; their events are logged while tracked.
• Tracking expires automatically.
• Live watch patterns in the Control Center.

What you get

• Map your existing Discord roles onto named positions — Co-Owner, Administrator, Moderator, Trial Moderator, plus specialist and shared staff roles.
• Don't have a suitable role? Generate a preset and Archivian creates it with a coordinated name, colour, permissions, and place in the hierarchy.
• The Quarantined role is classified here too, so Anti-Nuke knows which role to apply when it isolates a member.

You control

• Assign any existing role to any named position, or generate the missing ones in one go.
• Decide per specialist role — Community Manager, Developer, Employee — whether it counts as staff.
• Add any other staff-only roles that do not fit a named position.

What you get

• Central staff overview in the dashboard.
• Retire staff members while preserving their records.
• Time-limited join codes for inviting new staff.

What you get

• Each title carries a permission set you configure.
• Link a Discord role to a title so granting/removing the title assigns/removes the role automatically.
• Auto-grant rules for titles.

What you get

• Ownership- and condition-based rules, not just on/off switches.
• A permission library lets you compose permission sets from drag-and-drop presets.
• Basic and advanced permission editors.

What you get

• Put staff in one or more teams, each carrying additional permissions.
• Link Discord roles that are assigned and removed as members join or leave teams.

What you get

• Custom messages with optional links, delivered via dashboard and Discord.

What you get

• Real-time collaboration on rich documents.
• Access control by member, title, or team.

What you get

• Define multiple ticket types for different purposes.
• Lock/unlock tickets, invite specific staff (granting them channel access), and archive resolved tickets.

You control

• Per-type settings for visibility and behavior.

What you get

• Portals are published into Discord channels as interactive entry points.

What you get

• Users browse and inspect their past tickets from their account.

What you get

• Browse cases made on you (where servers allow it) and create appeals from them.
• Check whether you're banned in a server, and start a retroactive appeal.
• Browse your ticket history across servers.

What you get

• Opt out of alert types you don't want — or opt in to extra delivery channels like email.
• Public email preference management, no login required.

What you get

• Records which titles you held, where, and for how long.
• Optionally public, so others can verify authentic moderation experience.

What you get

• Complete verification tasks in your personal dashboard to raise Archivian's trust in you.
• Per-server thresholds still apply — each community keeps control.

What you get

• Discord audit log events are captured and stored on Archivian's side, beyond Discord's 45-day window.
• Archivian's own case and bot audit logs are stored forever.

What you get

• Alerting per case type and per resource type.

You control

• Route each alert type to its own Discord channel, or rely on a default channel.

What you get

• Alerts include who made the change and what was changed.

What you get

• Composable live windows: message feeds, watchers, moderation/audit feed, user inspection, and case creation.
• Built for active moderation sessions during busy hours or incidents.

What you get

• Step-by-step server setup wizard for initial configuration.
• Setup helper that sanity-checks your configuration.

What you get

• Voice channel joins and leaves are recorded in Archivian's custom audit logs.

What you get

• Moderate, configure, and investigate from the browser; the bot handles the Discord side.
• Real-time updates between Discord and the dashboard.

What you get

• Run a dedicated bot instance using your own bot token.
• The platform is already built to support this; some work remains before you can set it up yourself. Express interest if you want it prioritized.
• This will be a paid feature when it launches (pricing is not decided yet).

What you get

• REST API for third-party integrations and custom tooling.

What you get

• Provide a webhook URL and receive structured data for synchronization with external systems.

What you get

• The API is intended to support full data export — and support will help if something is missing.