Default channels

Archivian has three default channels it uses when no per-feature override is set. This page explains what each one is for.

Feed channel

This channel is used for less important alerts and the general feed, audits, and events, unless an override is specified elsewhere.

These are often the kinds of alerts produced frequently — things like message edits and Auto-Mod violations. Most of the time they don’t require any intervention from staff. That’s in contrast to the more important alerts (such as new case appeals and tickets), which are less frequent and do require staff to engage.

Alerts channel

This channel is used for more important alerts, unless an override is specified elsewhere.

Think of things like case appeals and tickets — alerts that explicitly require intervention from staff, such as resolving a report or ticket, or reviewing an appeal. These are usually created much less frequently than the “spammy” feed alerts described above.

Overwriting existing channels

Both the Feed and Alerts channel settings offer an Overwrite existing channels option.

Enabling it is recommended if you’ve never adjusted Archivian’s alert channels. Even if you have, you likely want all of these alerts to go to a single channel anyway.

Various systems in Archivian can produce alerts, and many of them support their own overrides. If you’ve ever used one of those, the channels they point at may be overwritten by the channel you specify here. (If it’s the same channel, it doesn’t matter, of course.)

When left disabled, only channels with no setting defined yet are configured to use this channel — any overrides you’ve already specified are preserved.

News channel

This channel is used for sending news about Archivian’s development, announcements, system messages, and so on.

Sensitive information is never sent here, so it’s technically safe for anyone to view — though it’s likely only useful for your staff.

You can opt into receiving updates from Archivian, broken into categories so you only hear about what you care about:

• Features — new, deprecating, or significant feature announcements (bigger features and additions, not small changes or bugfixes).
• Changelog — big and small changes such as bugfixes, tweaks, and changes to existing features; generally every time something changed or fixed is released.
• System Events — upcoming maintenance, downtime notices, and general information such as provider outages that caused restarts.
• Betas, Experiments, Opt-Ins — early access to features and opportunities to sign up for tests and give feedback that shapes how things work.
• Sneak-Peeks — occasional experimental pictures, demos, or short written messages about what’s being worked on.