Glossary
A glossary of special words used in Archivian. Plurals (e.g. “cases”, “entries”) mean the plural of the singular term.
Appeal File
Section titled “Appeal File”A file attached to a case appeal. An appeal can have multiple files, depending on your premium tier.
Archived
Section titled “Archived”A resource that has been archived — softly deleted, but kept around for authenticity, preservation, or just-in-case. Anything archived is meant to be treated as if it never existed (an archived ban case, for instance, means the user should be regarded as never having been banned). Archived resources can be restored.
Auto-Mod Template
Section titled “Auto-Mod Template”An Archivian concept: a blueprint for a Discord Auto-Mod rule that you can activate in a server. It contains pre-made patterns that match against messages. See Discord Auto-Mod Templates.
A native Discord feature (also an Archivian command) that removes a member from the server for a given reason until they’re unbanned. It can be permanent or temporary. Discord bans also affect IP, so a banned user can’t simply re-join with another account without a proxy or VPN. See Ban under case type.
A punishment or remark on a target’s “record”. Archivian has several case types, so a case can be any of them. A case can have multiple entries and files, plus links and extra metadata.
Case Appeal
Section titled “Case Appeal”Often just called an appeal. If a case is visible to its target and appeals are enabled for it, the target can appeal it — commonly to get a ban lifted. Appeals can be made on any case except a note.
Case File
Section titled “Case File”A file attached to a case. A case can have multiple files (limits depend on premium tier) — a good way to keep proof. Files are stored on Archivian’s servers, so you don’t rely on them sticking around in Discord.
Case Links
Section titled “Case Links”Ambiguously refers to either a linked case or a linked user — not a URL.
Case Type
Section titled “Case Type”Any case of one of Archivian’s types: Ban, Kick, Timeout, Warn, or Note.
A case can have multiple entries. An entry is like a “reason” for the case (for example the reason for a ban) — but unlike other bots, Archivian allows several, so staff can add multiple updates to a case for any reason.
Either a case file or an appeal file. Depending on premium tier there may be limits on how many files can be attached and how big each can be. A file records when it was uploaded, who uploaded it, who last edited it, and its visibility.
A native Discord feature that immediately removes a member for a given reason — but doesn’t stop them from re-joining with an invite. Often used when a legitimate user has lost access to their account or is compromised.
Ladder
Section titled “Ladder”The ordered set of rungs a strike pool escalates through, from the gentlest consequence to the most severe. A member climbs it as their strike points build up, and each rung fires on the way past. Also called the action ladder. See Strike System.
Linked Case
Section titled “Linked Case”Two cases linked together for any reason, to build context or a chain of related cases (e.g. a ban plus bans on the same user’s known alternate accounts) instead of writing “refer to case #3” in an entry.
Linked User
Section titled “Linked User”A Discord user who isn’t the target of a case but is related to it somehow — for example the reporter, the victim of a scam or harassment, or the instigator of a fight. A linked user has a label (up to 32 characters) and a Discord user; linking has no negative effect on that user.
Managed Rule
Section titled “Managed Rule”A bridge between an Auto-Mod Template and a Discord Auto-Mod rule — i.e. a template activated as a rule in your server. This happens when you subscribe to a template (manual or automatic updates). “Managed” means Archivian watches that template for updates. See Published & Mounted Templates.
Message Policy
Section titled “Message Policy”The internal (code) name for a message rule; the dashboard UI calls it a message rule.
Message Rule
Section titled “Message Rule”How you configure tracking and alerting for messages that are created, edited, or deleted. Rules can be nested for more specific contexts (by author, channel, or roles), and each can explicitly enable or disable tracking and alerting. See Channel Management.
The older term for silencing a member. The modern equivalent is a timeout. Historically done by assigning a role that lacked permission to speak or write.
A case type meant as a generic note shared among staff (like Discord’s profile notes), built on the case system. A note does nothing to the user on its own, and by default the user isn’t notified.
Permission Node
Section titled “Permission Node”A single piece of permission that grants access to one or more things. It’s built from multiple permission sub-nodes. See Permission Nodes.
Permission Set
Section titled “Permission Set”A pre-made group of permission nodes that grants access to one or more things at once — like a keychain of keys you hand to a title. Browse them in the Permission Set Library. See Using Permission Sets.
Permission Sub-Node
Section titled “Permission Sub-Node”A part of a permission node, separated by dots. It can be highly specific, a
wildcard, or an extender — e.g. case.** (full case access) or case.*.create (create any case
type).
Permissions
Section titled “Permissions”Archivian’s custom permission system, independent of Discord. Only titles and teams can hold permissions; staff have none on their own (the server owner and administrators are exceptions). See Permission System.
Premium Tier
Section titled “Premium Tier”Which of Archivian’s tiers a customer is on — Free, Plus, or Pro. It doesn’t imply you need a paid plan. If you don’t know which tier you’re on, you’re most likely on Free.
Private Template
Section titled “Private Template”A private Auto-Mod Template. Every new template is private by default — only you (or, if created within a server, the server staff) can access it. Publishing it creates a public template.
Public Template
Section titled “Public Template”An Auto-Mod Template that was published. Public templates are visible on the internet; logged-in users can make their own copies, and servers can subscribe to updates. See Published & Mounted Templates.
Resource
Section titled “Resource”A generic term. In the context of cases, it usually means the case itself or one of its entries, files, or links.
Restore
Section titled “Restore”Bringing an archived resource back into existence (and back onto a user’s record, if applicable), provided you have permission to read and restore it. The act is called “restoring”.
One step on a strike pool’s ladder: a point score plus the actions that run once a member’s strike points cross into it going up. See Strike System.
Server Error
Section titled “Server Error”Also called a “Guild Error”. A generic error, bug, informational alert, or log entry that Archivian captures and may store for your server to see — sometimes caused by Discord (e.g. an unknown channel). See Server Errors.
Severity
Section titled “Severity”A named shorthand for how many points a strike is worth: Low, Medium, High, Extreme. Exists so staff can say how bad something was instead of picking a number out of the air. The levels can track your action ladder automatically or be set by hand. See Strike System.
Soft-Ban
Section titled “Soft-Ban”A trick to kick a member and delete their recent messages at once: instead of a kick, a ban is issued and immediately lifted, to leverage Discord’s native message deletion. Saves having to kick and purge separately.
Discord users who have been added as staff members on the Archivian platform. Being staff in your Discord server doesn’t make someone Archivian staff unless they’ve been explicitly added. See Adding Staff.
Strike
Section titled “Strike”A record that a member did something wrong, worth a number of points toward a strike pool. A strike stops counting when it is pardoned, when its lifetime runs out (unless marked permanent), or when it is absorbed by a ladder reset—in every case the record itself stays on the member. See Strike System.
Strike Absorption
Section titled “Strike Absorption”What happens to a member’s counting strikes when they reach the last rung of the ladder and the server has a reset configured: the strikes stop counting so the member can climb the ladder again, while their records remain for the history. Permanent points are never absorbed. See Strike System.
Strike Points
Section titled “Strike Points”The currency of the strike system. Every strike is worth a number of points, they add up on the member in a strike pool, and it is the running total — not the number of strikes — that decides which rung of the ladder they have reached. Points can expire, fade, or be marked permanent, so a member’s total moves on its own over time. See Strike System.
Strike Pool
Section titled “Strike Pool”An independent strike system: its own sources, its own ladder of rungs, and its own running point total on each member. A server can run several — spam on one, harassment on another — and their scores never add together. Which pool a strike lands in is decided by the reason it was issued under. See Strike System.
Target
Section titled “Target”The Discord user a case is being made on.
An upcoming/planned Archivian feature. A staff member can be in zero or multiple teams at once. Each team can automatically grant its members a set of permissions and a linked Discord role (added on joining the team, removed on leaving).
Temp-Ban
Section titled “Temp-Ban”A temporary ban. Not a native Discord feature. Bots use scheduling to make it expire.
Timeout
Section titled “Timeout”Discord’s built-in timeout feature (formerly known as “mute”). It prevents the user from typing in any channel or thread, and from speaking in voice channels.
Like a job title, or a Discord server role: it indicates a staff member’s position and gives them a set of permissions while they hold it. Without a title, staff have no permissions. A staff member can have only one title at a time. See Titles.
Un-Mute
Section titled “Un-Mute”Refers to undoing a mute or timeout.
Un-Timeout
Section titled “Un-Timeout”Refers to undoing a timeout. This is the modern term, used so as not to confuse it with the legacy mute.
A warning case type. On its own it does nothing to the user (unlike a ban, kick, or timeout)—it simply creates an official record that the user was warned. It’s common to enable a DM notification when a warning is issued.