Features Overview

Roadmap

Here's a list of things we're planning.


Archivian has a lot more unique features specialized for moderation than other bots, and we have unconventional behavior that we believe is a better way of doing things.

Staff, Titles, Teams

Staff members

Bring your entire community staff team on board the platform. Use the dashboard as a central place for information and task delegation. Retire old staff members, but keep their records.

Implemented

Titles

Give staff members titles, and with titles, comes permissions you configure. Link a Discord server role to a title, so that titles granted and removed automatically assigns or removes the respective guild role.

Implemented

Teams

Got many staff members? Put staff members in one or more teams. Give additional permissions that comes with teams, and link Discord server roles that are given and removed when you join or leave a team.

Staff Announcements

Announce to all staff members, those with a given title, or specific teams. Give a custom message, and link to any URL you desire.

Collaborative Documents

Live collaboration on rich documents, such as onboarding, guides, guidelines, brainstorming, upcoming features and more. Control document access to members, titles, or teams.

Permission Library

Archivian's permissions can be complex. A permission library lets you compose the perfect set of permissions by drag-and-drop of presets that give a set of permissions.

Implemented

Not Just for Staff

Browse Cases on You

If servers let you view the cases they created on you, you can find them all in your personal dashboard. From there, you might be able to create appeals.

Implemented

Skip the Gatekeeping

In your personal dashboard you can perform tasks to verify you're not a bot, which will help Archivian trust you more in servers that use its gatekeeping features (thresholds are still up to each guild though).

Your Staff Journey

Is moderation your thing? We store which titles you've had in which servers, and for how long. These records can be made public, so others can view authentic records of your moderation experience.

Opt-out of Alerts & Pings

Don't let us annoy you. While servers decide when they want to alert you (often via Direct Message), you can also decide yourself what you want to receive…

Opt-in to Alerts & Pings

…or maybe you can't get enough of alerts? Configure additional ways you want to be notified, and when, like sending you emails or produce alerts in your personal dashboard.

Cases, Entries, Files, Links

Note Case

A new type of case: Note, useful for shared notes among staff, like un-official verbal warnings.

Implemented

Marked Case

A new type of case: Marked, useful for marking users. Can perform automations, like adding/removing roles, ability to automatically generate another (e.g. a ban) if user is still "marked" after a given amount of time.

Configurable Behavior

You can decide if the bot tries to send the user a direct message or not. Per type of case you have options to toggle things like show creator, show reason for case, fallback to notifying in the channel, or even add a custom message.

Implemented

Enable Educational Tips

Are your staff new to Archivian? After a new case is created, you can enable displaying information like our built-in tips on entires, files, and links, or your own custom message.

Implemented

Instant After-Action Report

After a case is created, you can enable things like automatically showing 3 latest cases on the user, the success of the direct-message notification, and more.

Implemented

No dedicated unban/unmute types

Unbans and unmute isn't scattered. Bans and unmute are recorded in the original case automatically, so you have it all in one place. An entry gets added to the case, and tagged as the unban/unmute reason.

Implemented

Native Mute (timeout)

Archivian uses Discord's built-in Timeout functionality for muting, instead of the legacy way of role assignment, which required a dedicated role and configuration of channel/category permissions.

Implemented

Entries

Some cases need more than just a reason. Collaborate with your peers on adding more information through entries to a case.

Implemented

Files

Files are first-class citizens in cases. Attach a file, and we host it for you, no reliance on Discord needed. If you use a premium plan, we'll even automatically detect file links and add them for you.

Implemented

Linked Users & Cases

Link users to cases, such as victims or collaborators, with custom labels. Links can also be made between cases with any label, so that you always have context and meta information.

Implemented

Case & Resource Visibility

Want a specific case to be fully transparent? Make it public. Maybe just the files that are used as proof? You got it. You have fine control over how and when who gets to see what.

Implemented

Ownership & Condition Based Permissions

Fine-tuneable controls of permissions. Deny or allow staff members to do things on cases or resources, with precision like Can edit an entry in a ban case if the staff member made the case and made the entry .

Implemented

Archived Cases

Was a case wrongfully created? If you're strict about keeping records, it can be archived and hidden away, as if it never existed—but with the right permissions, you can view it, or even restore it.

Implemented

Archived Entries & Files

You can archive Entries and Files the same way you archive a case. Hidden away, but not deleted, and with the right permissions, can be viewed or even restored.

Implemented

Appeals

Appeals for Cases

Appeals are built in, and can be toggled per type of case. It can even be toggled on individual cases. If enabled, users can receive a button to go directly to appeal when they get notified of a case being made on them.

Implemented

Appeal Assignment

Want someone specific to handle an appeal? Assign them to it, which depending on their alert setting, will send them alert in the dashboard, email, and/or a notification in Discord.

Implemented

Assignment Permissions

Assigning staff to appeals will automatically give them access to read and edit appeals, and read the original case, if they previously didn't have permission to it.

Implemented

Progress

Let the appealing user know where in the process an appeal is. You have the ability to change status of appeal, which they can enable alerting for if they want.

Implemented

Files in Appeals

You can enable files to be uploaded in cases of a specific type, or overried per appeal. Allows staff and the appealing user to upload files that we'll host and archive.

Built-in Chat

Need to communicate with the user that was banned? Keep all records in the appeal by using a basic chat that can be enabled by default or on a per-appeal basis.

Implemented

Automated Resolving

Was the appeal accepted? Depending on the type of case, Archivian will automatically take care of it. Was the user banned? We'll unban them. Do they have timeout? We'll remove it.

Implemented

Alert on Create, Edit, and Delete

Case & Resource Changes

You can enable alerting when a case or resource (file, entry, link) is created, updated, or deleted, per type of case. For each resource, you can configure an output Discord channel, or rely on a default channel.

Implemented

Changes to Settings & Permissions

Configure alerting for when certain settings are changed, by whom, and what was changed.

Implemented

Automated Systems

Early Warning System

Get alerted when suspicious users joins the server, based on several factors, and triggered by your thresholds or manual triggers factors, such as account age, username and Discriminator originality, if user have avatar, and more.

Implemented

Reactive Early Warning System

Not only can you trigger alerting with the Early Warning System, but you can also configure automatic triggers, such as creating any type of case with pre-configured parameters like duration and reason.

Intercept Cases

Intercept Timeouts, Kicks, and Bans made using the native Discord functions or other bots, and automatically have cases created from them with whatever information is available.

Implemented

Keep Discord Audit Logs Plus Pro

Discord stores audit logs for 45 days. We store them for a year Plus or indefinitely Pro

Reliable Old Message Content

Sometimes bots won't tell you what the old content was, mostly because it's not saved for long, if at all. Archivian stores all messages, so you will know what the old or deleted content was. We also keep track of edits made to messages.

Implemented

Embeds & Attachments

Most, if not all, bots don't consider embeds and files in messages edited/deleted when people edit or delete messages. We have dedicated alerts for deleted files and deleted/edited embeds, a nd detect deletions via edits.

Implemented

View Cached Deleted Images Plus

We trigger caching of Discord images, so that any time an image is deleted, there is a chance (not guarantee) that it is possible to view the image afterwards.

Discarded

Automatically Store Files

Archivian will automatically store all file attachments sent in the server for up to 2 weeks. This means that any deleted files can be viewed at any time, with the possibility to permanently delete images from our storage.

Implemented

Voice-Chat Features

Join-Leave Logs

Log when users leave or join voice channels, for 45 days Free , 1 year Plus , or indefinitely Pro .

Reconnect Cooldown Plus

Prevent users from using the sound-effects of joining and leaving as a means of spamming. Create a cooldown period where user cannot move to other channels or re-join a channel.

User & Message Reporting

Message Reports

Your members can report messages. After a few reports (a configurable threshold), a message report will be submitted to your staff.

User Reports

Like with message reports, users can also be reported, and given enough reports, a user report will be created in the dashboard.

Reactive Auto-Moderation

Configure automatic actions when user or message report thresholds are met, like delete message (or all identical ones sent past 48 hours), time-out the user, and more.

Biased Reporting

Give more credibility to reports by users with certain roles, making report thresholds be met faster—or outright ignore reports made by certain roles, or the lack thereof.

Change History

On reported messages we store the message in case of deletion, and keep records of its changes. We store text, files, and embeds on our end.

Punitive Evidence Tampering

If the user edit/delete their own message that has been reported, a configurable action can be triggered, if the message had a certain report threshold.

User Report: Messages Plus

When a User Report is submitted, we preserve delete messages and track changes of all the messages we have stored on the user.

User Report: Messages Pro

Like with User Report: Messages Plus , but we start immediately on first report, instead of waiting until it has enough reports to be submitted.

Message Report: Context Pro

On first Message Report, we store and track changes of up to 50 messages sent before the reported message, so that you have context for the reported message.

API, Export, Import, and Integrations

API Available

We plan on having an open API so you can manage settings, query cases, etc. programmatically.

No Vendor Lock-In

We don't want to lock you in with Archivian, so if you ever want to move on, feel free to use the API to export data. Feel free to ask support if there's something we're missing.

Webhook

Got a custom system that you want to synchronize warnings and other cases? Provide a webhook and we'll send it data any time we would potentially do channel alerts.

Import Cases

Want to move over to using Archivian? If you have a CSV file of cases, you can import them into Archivian.