Team and permissions
A server's Team page says who can do what with its Blueprints. Only the server's owner and its managers (the members with Administrator or Manage Server on Discord) change it.
The permissions
Each permission opens one action, and only one:
| Permission | What it allows |
|---|---|
| Ask for access | Ask for access from the servers page |
| Dashboard access | Open the server's dashboard: the home, Bot and Limits |
| View the Blueprints | The list, the content and the history, without changing anything |
| Create Blueprints | Create a Blueprint, or duplicate one |
| Edit the Blueprints | The draft, the name, the description, the tags, the versions |
| Delete Blueprints | Delete a Blueprint |
| Run tests | Start a test mode session; needs editing |
| Deploy the Blueprints | Put online, pause, resume |
| View the executions | Every execution, with the data handled, like members' messages |
| View the analytics | The statistics of the server and of each Blueprint |
| View the Variables | The values on the Variables page |
| Edit the Variables | Correct, erase, reset values |
| Tester | During a test session, their actions trigger the draft |
A permission sometimes needs another: without dashboard access, nothing else counts; without viewing the Blueprints, you can neither edit nor deploy them.
Three states, like on Discord
Each line of the page (@everyone, a role or a member) says, for each permission, Allow, Deny or Inherit, like a channel's permissions on Discord. For a member, the first answer wins:
- The owner has everything, but Tester.
- Their own line, if they have one.
- Their roles: a role allowing wins over a role denying.
- @everyone, the base of the whole server.
- A manager has everything by default, but Tester.
- Otherwise, the permission is denied.
A member's panel shows, for each permission, what decides it for them: "Allowed · by @Moderation", "Denied · manager".
@everyone
The @everyone line counts for the whole server. At first, it only allows Ask for access: deny it to stop access requests from the whole server. You can also open a permission to everyone there, the analytics for instance; opening to the whole server what shows members' data or changes something asks for a confirmation. Tester isn't given through @everyone: use a role.
The owner and the managers
The Server owner and Server managers lines show what they hold: everything (by default, for the managers), but Tester. They can't be changed; each turns Tester on for themselves there. Who is a manager changes on Discord, in the server's roles.
Tester
Tester opens nothing in the dashboard: during a test mode session, it makes your own actions on Discord trigger the draft instead of the version online. That's why it's an exception to the rules below:
- nobody has it by default, not even the owner, and @everyone doesn't give it;
- the owner and each manager turn it on for themselves, on the Server owner or Server managers line; a denial someone else put on their line doesn't stop them;
- a member who doesn't manage the server has no Team page: a manager gives it to them, on their line or through a role ("@Testers").
Restricting a manager
A manager has everything by default, but their own line can deny them a permission. A role's denial only reaches them if the role's line ticks Applies to managers too: a role everyone has can then deny members something without taking anything from the managers. The box says which managers it would restrict.
The rules
- The owner's line is theirs alone.
- You don't change your own permissions, but Tester, which everyone turns on for themselves: on your line, or on Server owner or Server managers if you are one.
- You don't give a permission you don't hold.
- A change that would take a permission from you (a role you have, @everyone) is confirmed: only the owner or another manager will be able to give it back. A change that would give you back a permission taken from you is refused.
Giving access
Give access adds a role or a member, searched by name or by Discord ID (for someone not on the server yet). Their line starts with dashboard access; a role or a member who manages the server starts with everything you can give. You pick the rest right after, on their line.
A member without access can also ask for it from the servers page, with a word for you. Accepting opens the dashboard to them; you then set what they can do there. With dashboard access alone, the home tells them no permission is given yet.