Title Permissions: Basic & Advanced

Quick introduction

Features and resources in Archivian have their own permissions. You assign these permissions to titles, then give a staff member a title — similar to Discord, where you enable a permission on a role and assign the role to a user. One difference: Discord lets a user have multiple roles, whereas an Archivian staff member can only have one title at a time.

You get a few pre-made titles out of the box for convenience, but you can change them or create your own. Right now you can only pick pre-made permission sets from our library, but a fully bespoke setup is technically possible — just reach out and we’ll set it up with you.

A deeper dive

Permission sets

We create and maintain pre-made permission sets you can enable on a title. Each set targets one or more features, or is designed for a typical group of staff (Moderators, Appeal Reviewers, and so on). Composing these sets is the main way to customize a title’s permissions. See Using Permission Sets.

Each set contains one or more permission nodes, which are themselves very flexible and give a lot of control.

Advanced permission use-cases

Advanced permissions let you control the raw permission nodes on a title yourself. This is useful when:

• you need much more control than the permission sets offer;
• staff with the title lack the permission to run a specific command, and you want to grant just that; or
• you know the permission system well enough to build it yourself.

Each permission node is specially formatted text our system parses to decide whether you can use a feature. A set may consist of multiple nodes, and a title may be composed of multiple sets.

When a staff member runs a command they don’t have access to, the bot says access was denied — and tells you exactly which permission node they’d need. You can copy that node string into the raw permission editor on the Advanced tab to grant access to that specific thing.