Archivian

• Use it like any other bot's case system. Leverage its super-powers when you need it
• Five case types: note, warning, timeout, kick, and ban
• Collaborate with staff on cases with multiple entries per case instead of just a fixed reason
• Unbans and unmutes are recorded back into the original case as tagged entries, instead of scattered records
• Automatically detect bans, kicks, and timeouts created by other means, and generate cases from it^[1]
• Attach files directly to cases, useful for storing proof or whatever you like
• Detailed tracking of edits to the case
• Link cases to each other with a label, like a related ban or a warning before a timeout
• Link other users to cases with a label, like a victim of a scammer that got banned
• Show/hide cases, entries, and files to the user so they can re-visit the case any time in their own personal dashboard^[2]
• Archive cases, entries, or files that should no longer be visible, but should be kept for record purposes
• Incredibly flexible settings per type of case: DM notifications, whether the creator is shown, whether the reason is shown
• Fall back to an in-channel notice when the member has DMs closed, with your own custom message
• See recent cases made on the user when you create cases on them
• Create custom tips/info for your staff per type of case, e.g. a reminder to attach proof when a ban is created
• Use pre-made tips for staff when they create cases, teaching and informing them of the possibilities

• Files are first-class citizens on cases, hosted by Archivian with no reliance on Discord's CDN
• Your evidence does not stop working when a Discord attachment link expires
• Archive a file to hide it from normal views while keeping it on record
• Restore archived files again when someone with the right permission needs them
• Control per file whether the affected user gets to see it in their own dashboard

• Dashboard tool for banning, kicking, or timing out many members in one go
• Every action still produces a proper case record, same as if it were done one by one
• Useful after a raid, when you have a list of accounts to clear out

• Overview of moderation activity built into the dashboard
• Counts per case type, recent activity, and trends over time
• Spot whether things are calming down or heating up

• When users get alerted, they can create appeals with the click of a button^[1]
• No second server, no forms, no third-party service — appeals live in the users' own dashboard
• Appeals are linked to cases, so you can see them directly when browsing cases
• Built-in livechat on the website dashboard, so staff and appealing user can chat in real-time^[2]
• Assign appeals to staff, automatically granting them access to the appeal and read access to the associated case
• Move appeals through your own process with statuses, and let users get alerted when the status changes
• Reject or approve an appeal, to automatically undo if approved (unban, lift timeout)
• Let users check if they are banned in your server and appeal retroactively — even for bans from before you started using Archivian^[3]
• Control the ability to appeal per type of case, with a possibility of overrides per case
• Allow or disallow further appeals when rejecting an appeal

[1] Configurable per type of case [2] Can be on by default, or enabled per appeal [3] Configurable via case settings

• Users can log in with their Discord account and have their own personal dashboard
• Here they can see cases on them from all servers, appeals they created, and more^[1]
• Create appeals directly from the case they are browsing

[1] If Archivian was used, and if the server lets them see it

• Members build up points; when the total crosses a rung's threshold, that rung fires
• Up to 25 rungs per pool, each with its own threshold, re-arm score, and cooldown
• Rungs use hysteresis: once fired, the score must fall back below the re-arm point before it can fire again

• Rung Actions

  What a rung can do when it fires

  • Add roles to the member
  • Remove roles from the member
  • Create any type of case on them
  • Send a message, as a DM or in a channel
  • Alert staff so a human reviews it instead
  • Combine several actions on a single rung

• Preset Reasons & Severity

  Consistent pricing for offenses

  • Define up to 20 preset reasons, each with its own point value
  • Override the point lifetime per reason
  • Up to 10 custom severity levels to let staff mark how bad an incident was
  • Severity can track the ladder automatically, or be set by hand

• Lifetime, Expiry & Gradual Decay

  Choose how the past stops mattering

  • Points can count fully for their lifetime and then expire
  • Or fade gradually along a curve you drag into shape
  • Or never expire at all
  • Make strikes heavy while fresh and light later — or the other way around

• Biases & Multipliers

  The same offense does not have to cost everyone the same

  • Charge more for brand-new Discord accounts, with your own age window and curve
  • Charge more for members who just joined the server
  • Per-role weights to go lighter on trusted members
  • Floors and ceilings so multipliers never compound into nothing — or into everything
  • Every strike shows its breakdown: which factors changed the points, and by how much
  • See the point range a strike can land in before you save the config

• Multiple Strike Pools

  Independent ladders that do not pollute each other

  • Run several strike systems at once — spam on one ladder, harassment on another
  • Scores are not additive; each pool tracks its own running total per member
  • Which pool a strike lands in is decided by its source
  • One auto-mod rule can feed several pools, charging each independently
  • Deleting a pool keeps the strikes as historical records
  • The ladder editor shows every pool side by side on one score scale

• Sources

  Where points come from

  • Manual: the /strike command, the member right-click menu, or the message right-click menu
  • Automatic: point the ladder at individual Discord Auto-Mod rules, one at a time
  • Automatic: Archivian Auto-Mod checks — bad links, bad images, server invites, text patterns, cross-posting, per-member spam
  • Set points, lifetime, and target pool per rule or check
  • Rules renamed in Discord stay in sync; deleted rules are marked instead of silently dropped
  • Choose whether re-editing a still-violating message costs points again, or at most once
  • Only checks that name an individual can cost points — channel-wide spam is excluded on purpose^[1]

• Review & Correction

  Strikes are reviewable, not final

  • /strikes browse and /strikes inspect to review history right in Discord
  • Pardon a strike to keep the record but remove its points from the total
  • Un-pardon to reverse that, with a separate permission for "the strike was right after all"

• End of the Ladder

  What happens when someone tops out

  • Seven ways to treat the score at the top rung: wipe it, keep a percentage, or drop to the middle and climb again
  • Optional permanent point banking, so repeated tops keep adding up
  • Cooldowns so one incident is never charged twice

• Exemptions & Protected Roles

  Keep the ladder away from the wrong things

  • Exempt specific users, roles, channels, apps, and your staff roster
  • Roles with sensitive permissions are protected: rungs neither grant nor strip them
  • Choose which permissions place a role out of reach

• Build modules in a dashboard editor, with your own triggers, thresholds, and actions
• Overview dashboard for all your auto-mod systems in one place
• Always ignores messages by your own staff
• Create exceptions per channel or for members with specific roles
• React with sending a message, by replying to user, DM them, and/or send the message to a fixed channel
• Delete message(s) that are in violation
• Assign and/or remove roles from members when a violation is detected
• Create any type of case on the violating members
• Feed violations into the strike system so they cost points

• Discord Server Invites

  Detects invites to Discord servers.

  • Follow links and redirects to properly assess if it is an invite
  • Create exceptions for specific servers, or just exempt specific server invite codes
  • Exempt servers that have specific features, like being Discoverable
  • Exempt invites created by specific users, useful for dedicated delegates from your server

• Text Patterns

  Simple text pattern matching against message content

  • Check message content against words or phrases
  • Detect start-of or end-of words and phrases
  • Detect exact words or phrases
  • Detect if a word or phrase matches anywhere

• Bad Links

  Catch links you do not want in your server

  • Acts on links that should not be posted in your channels
  • Can be routed into a strike pool with its own point cost

• Bad Images

  Works together with the image blocklist

  • Acts on images matching what your server has blocked
  • Can be routed into a strike pool with its own point cost

• User Spam

  Detect when a single member sends too many messages too fast

  • Configure how many messages in a given time window to trigger this
  • Tracks messages from the user across all channels
  • Waits for a few seconds to see if they spam some more before taking action
  • Automatically cleanup by deleting all the messages that contributed to the spam trigger

• Channel Spam

  Detect when a channel receives too many messages too fast

  • Configure how many messages in a given time window to trigger this
  • Each channel is tracked separately
  • Waits for a few seconds to see if they spam some more before taking action
  • Automatically cleanup by deleting all the messages that contributed to the spam trigger
  • Temporarily enable channel-slow mode for a limited amount of time to slow things down

• Cross-Posting

  Detect a user sending the same message across multiple channels

  • Configure how many channels in a given time window to trigger this
  • Waits for a few seconds to see if they spam some more before taking action
  • Automatically cleanup by deleting all the messages that were cross-posted

• Browse the public library of battle-tested rules — you do not even need to log in to look
• Subscribe to templates and receive auto-updates, either automatically or with a simple update button
• Create your own Auto-Mod templates from your personal dashboard and re-use in all your servers…
• … or create unique templates that the server itself owns, so it is not bound to specific users
• Publish your templates for the world to see and import for their own use
• Create copies of templates you like and adjust them to your own needs
• Import your existing Auto-Mod rules with ease, and one-click import back into Discord
• Create and maintain multiple templates that can lay dormant until you need it (since Discord allows max 6 at a time)

• We store all the auto-mod violations that are triggered
• Violations are deduplicated and grouped, even when Discord emits several events for one violation
• Browse historic records of auto-mod violations per user and per rule
• See details of the violation, like matched content and what actions were taken
• See the auto-mod violations a user has made when you inspect them

• Messages, every edit, and every deletion are stored on Archivian's side — not in a cache that resets
• Browse files that were removed from messages, whether the message was deleted or the file removed
• Detect whether text was edited or removed, files removed, embeds replaced; not just if messages text deleted or edited
• Dedicated alerts for deleted files and for deleted or edited embeds
• Context-specific tracking: set exceptions for very specific scenarios, down to a precision like "store if sent in channel, member has this role, and it is this user"
• Tracking policy per type of event: message created, message edited, message deleted
• Set file and message tracking and retention period per context
• Enable anonymization of messages: store all details except the author ID

• Archivian keeps a copy of files uploaded for up to several months^[1]
• When files are deleted, you can see which ones in a dedicated view
• Detect whether the file was removed or the message was deleted
• Permanently purge stored files from Archivian's storage when you need them gone

[1] Configurable up to 3 months after creation, and up to one month after deletion

• Target a specific channel, or perform a global purge
• Use filters to limit messages to be deleted: from user, content pattern, specifically with or without files, max messages, between two message IDs, until message by ID, and more…
• Test deletion to make sure your filters are correct. See messages that would match
• Deleted messages stored in a dedicated message collections for reviewing later

• Triggered when messages gets bulk-deleted, via Archivian or other means
• Creates a collection of all the messages that got deleted^[1]
• Browse the message collection in the dashboard to see which messages got deleted

[1] Messages sent after Archivian joined, and has the tracking enabled

• Discord audit log events are captured and stored on Archivian's side, past the 45-day window
• Archivian's own case and bot audit logs are kept indefinitely
• Look up what happened months ago, when Discord can no longer tell you

• Voice channel joins and leaves are recorded in Archivian's custom audit logs
• Useful when an incident happened in voice and you need the timeline

• Lets members vote with reactions whether Archivian should delete a message
• Specify threshold needed to be met for vote-deletion
• Flexible biases to award more votes for certain roles
• Block specific roles or members from being able to vote after abusing the system
• Choose where in the server vote-deleting applies

• Archivian automatically blocks known scam images out of the box
• Ability to configure custom list of images that should not be allowed to be posted
• Register false-positives for images that are too close to a blocked one, but should be allowed

• Simple right-click menu on users/messages to report them
• Create your own types of report reasons
• Optionally prompt user with modal to fill in more details
• Threshold-based: staff get the report once enough members have reported
• Enable detailed tracking of members that are reported
• Store state of messages when they are reported, and tracks every change made to it, for complete history
• Reported messages are preserved on our side — text, files, and embeds — in case they get deleted
• Messages from a reported user are tracked too, so you get context and not just an accusation

• Act automatically when a report threshold is met: delete, timeout, and more
• Delete just the reported message, or every identical message the user sent in the past 48 hours
• Choose which actions happen at which thresholds

• Reports from members with certain roles count for more, reaching the threshold faster
• Ignore reports outright from specific roles — or from users with no roles at all
• Keeps brigading accounts from driving your moderation queue

• Watches public responses from apps members installed on their own account — apps that never joined your server
• Scores members and apps separately, so it catches one member cycling through many apps and many members hammering one app
• Heat fades on a half-life instead of resetting, so ten uses in seconds reads very differently from ten across an hour
• Low, Medium and High levels, each opening one reviewable incident with the member, the app, and the evidence
• Staff controls per incident: Clear, Escalate, Punish, Mark hostile, or Exempt
• Actions per level: staff alerts, add/remove roles, timeouts, vote-delete, deleting the tracked app output, kick, or ban
• Apps marked radioactive queue their next users as contained
• In severe incidents Archivian can temporarily revoke "Use External Apps", restoring it only to the roles that had it
• Testing mode observes and alerts without enforcing, so you can learn what normal app usage looks like first
• Periodic standing summaries list hazardous apps and open incidents, with bulk defusal buttons
• Trust discounts for account age, time in server, trusted roles, app age, and Discord-verified apps — with floors and ceilings
• Exceptions for specific apps, members, roles, and channels; your staff roster is exempt by default
• Custom messages per level, sent in-channel, as a reply, by DM, or to a chosen channel
• Release apps automatically after a set time, or keep full manual control

• Threshold-based detection across channels, roles, webhooks, emojis, stickers, soundboards, and bans
• Set your own threshold and action per trigger
• Detailed logs show exactly what tripped, and granular flags explain why an action was skipped
• Learning mode evaluates your configuration without any live consequences
• Bypass lists for trusted users, roles, and staff titles
• Request-based temporary bypasses for when someone legitimately needs to restructure things
• Works with the Quarantined role you classify in role management, for isolating a member

• Snapshots cover settings, channels, roles, webhooks, emojis, stickers, soundboards, and bans
• Roll back the whole server, or recover specifically from a nuke
• A rollback ledger keeps an audit trail of every restoration
• Progress tracking for long-running snapshot and rollback jobs

• Lock channels and whole categories in a single action
• Two modes per preset: read-only (no sending, reactions, voice, or threads) or completely hidden
• Save reusable lock presets with your channel and category selections already made
• Start and lift from the dashboard, or with /lock and /unlock in Discord
• Lift one channel or the whole preset — previous permissions restore exactly
• Every lockdown and lift is recorded in the audit logs
• Built-in debugger explains why a specific user can, or cannot, interact during a lockdown
• Separate permissions for managing presets versus actually starting and lifting lockdowns

• Challenge-based verification before a new member gets access
• Delivered by DM, or on a public dashboard page
• Fallback channel method for users who have DMs closed
• Backed by a captcha challenge pool
• Configurable thresholds and delivery behaviour

• Users get a trust-score based on several factors: account age, username originality, avatar presence
• When a score is too low, send an alert for staff to review the user
• Configurable threshold. Use global average trust score or the average of your own server as an indicator
• Choose which factors matter to you
• Show recent cases on the user if they have any, to highlight repeat offender re-joining

• Bait roles that trigger an automatic kick or ban when claimed
• Catches self-bots and automated accounts that skip past your join gate
• Normal members never touch it, so false positives are practically zero

• Put a member under watch when you suspect trouble; their events get logged while tracked
• Tracking expires on its own, so watches do not pile up forever
• Live watch patterns show up in the Control Center

Staff Roster

• Central staff overview in the dashboard
• Time-limited join codes for inviting new staff^[1]
• Retire staff members while preserving their records
• Create custom titles for your staff, which act as a role. E.g. Moderator, Trial-mod, Head-Administrator
• Assign a default title for new staff members
• Connect a Discord role to a title, so granting or removing the title moves the role too
• Auto-grant rules for titles

Server Role Management

• Map existing roles onto named positions: Co-Owner, Administrator, Moderator, Trial Moderator, and more
• Missing a suitable role? Archivian can generate the preset roles with coordinated names, colors, permissions, and hierarchy placement
• Decide per specialist role — Community Manager, Developer, Employee — whether it counts as staff
• Add other staff-only roles that sit outside the named positions
• Classify your Quarantined role here, so Anti-Nuke knows which role to apply when isolating a member
• Classifying a role never grants it to anyone — it only tells Archivian what the role means

Permission System

• Each title gives certain permissions
• Pre-made titles are generated when you add Archivian, offering you a jump-start
• Leverage Discord permissions for ease, or take full control of the permissions^[2]
• High-precision permissions can be used to give broad or very narrow scopes of permissions to your staff^[3]
• Condition-based rules, like "can edit an entry in a ban case if they made both the case and the entry"
• Compose permission sets from drag-and-drop presets in the permission library
• Basic and advanced editors, so you only meet the complexity when you ask for it

• Composable live windows you arrange yourself
• Message feeds, watchers, and a combined moderation and audit feed
• Inspect a user and create a case without leaving the view
• Built for active moderation during peak hours or an ongoing incident

• Discord alerts when cases, entries, files, or links are created, edited, or deleted
• Alerting per case type and per resource type
• Route each alert type to its own channel, or just use a default
• Alerts when Archivian settings or permissions change, naming the person responsible and what changed

• A real web app, not a settings page: moderate, configure, and investigate from the browser
• Home view with recent cases, appeals, reports, and auto-mod violations
• Real-time updates between Discord and the dashboard

• Guides you through adding the bot in steps
• Clear and simple instructions per step, showing you what to do
• Detailed explanations per step if you want to learn more
• Comes pre-configured with common things you'd want
• Setup wizards and configuration health checks take you from zero to configured safely

• We inspect your server's setup and list recommended changes
• Highlights what server settings you should change for better security & general recommendations
• Tells you what to change and why it is recommended
• Implement with 1 click, or follow guide to do it manually

• Create multiple types of tickets — support, applications, whatever intake you need
• Per-type settings for visibility and behaviour
• Create portal messages with a button users can click to start a ticket
• Creates new private channels per ticket in a category
• Add users to ticket channel, and invite specific staff to grant them access
• Close tickets, making it read only, re-open at any time
• Archive tickets to delete the channel and store the conversation

• Members keep access to their ticket history across every server that uses Archivian
• They browse and inspect past tickets from their own account
• Transcripts stay readable after the channel is closed and deleted

• Normal users can log into the Archivian dashboard to access a personal dashboard
• Browse cases made on them from any server that uses Archivian
• Browse appeals they have created, and see its current status and if actions are needed
• Check whether they are banned in a server, and start a retroactive appeal
• Browse their ticket history across servers
• Manage their own personal Discord Auto-Mod templates
• See overview over servers that they are staff in

• Discord DM, email, or dashboard alerts — their choice
• Opt out of alert types they do not want, or opt in to extra channels like email
• Email preferences can be managed publicly, without logging in