Permission System

Archivian’s permissions work independently of Discord — anything you do in Discord has no effect on Archivian permissions, with a few exceptions:

• The server owner has all permissions by default (tracked automatically).
• Administrators have the same permissions as the owner by default (also tracked automatically), except that really dangerous actions — for example “Purge & Leave” — can only be used by the owner.

Staff, titles, and teams

Staff have no permissions when first added — all they can do is see that they’re staff in the server, see the titles, and see the other staff. To get any other permissions, a staff member must be assigned a title or a team, and that title or team must itself have permissions assigned.

You can make a title the default, so any newly added staff automatically receive it.

Permission hierarchy

Discord has a hierarchy in its server roles; Archivian does not. There is no title (or team) hierarchy — no title outranks another, and the same goes for teams. They’re all equals, though their permissions may differ.

Defining permissions

There are three ways to define a title’s or team’s permissions. All three inject themselves into a title, so you can use all of them at once — the goal is to balance out-of-the-box ease with complete control when you want it.

1. Preset permissions

Preset permissions can’t be modified by anyone, but they can be enabled or disabled per title. They only exist in a title if you used one of Archivian’s template titles. When enabled, they let Archivian add permissions for new features to the title (where it makes sense), so you don’t have to maintain it.

2. Permission sets

Permission sets are small groups of permissions targeting a specific feature or purpose — like small modules you add to a title to rapidly build out its permissions. For example, one set might grant read access to all archived cases, entries, and files, while another grants the ability to restore them, and another to delete them.

Like preset permissions, these sets can’t be modified by anyone and are maintained by Archivian, so a set may gain new permissions when new features ship. Behind the scenes, each template title is actually built from one or more permission sets.

3. Custom permission set

This is a list of permission nodes you maintain yourself. You can let Archivian maintain the title, run a fully custom one, or anything in between (preset permissions plus permission sets plus your own nodes).

You define your custom permission set inside each title using the Permission Editor — a text box where you write the permission nodes. Custom permission sets aren’t shareable between titles the way permission sets are, but you can copy one and paste it into another title.