Roles and permissions: who can see and change each board

Your server already says who is who with Discord roles. KanbanCord uses them, so the right people see and change the right boards from the moment you add the bot, and you can fine-tune it when you need to. This guide covers the defaults, how rules are added, and exactly how KanbanCord decides, with examples for each case.

Out of the box

What someone may do follows the Discord permissions their roles give them, each step adding to the one before:

  • View Channels: see boards and their tasks.
  • Send Messages: also create and move tasks, comment, put labels on tasks, and assign themselves.
  • Manage Messages (moderators): also edit and delete tasks, and assign other people.
  • Manage Channels: also manage a board's columns, labels, priority levels, details and permissions, post boards in channels, and read the audit log.
  • View Audit Log: see boards and read the audit log.
  • Manage Server: everything above, plus creating and deleting boards and the server's features and permissions.
  • Administrator and the server owner: everything, always.

Nothing needs setting up, and when someone gets or loses a role in Discord, KanbanCord follows straight away.

Fine-tuning

To change who may do what, a server manager switches on Custom permissions with /kanbancord features. Then, on the website:

  • Server-wide rules say what each role may do on every board: create tasks, move them, assign others, delete, manage columns and more. The defaults above are rules too, one per Discord permission, and can be changed like any other.
  • Board rules change that for one board, for example to make a board only visible to a Staff role.
  • Per-person rules make exceptions for one member, whatever their roles.
  • Quick setup covers the common cases in one step, for the whole server or one board: everyone contributes, members view and staff edit, or staff only.
The server's permission rules on the website: what each Discord permission allows, from View Channel to Manage Server, plus a rule for the Organisers role.
The defaults, grouped by Discord permission, and a rule added for one role.

Each rule either allows or denies one thing. People who may change permissions cannot give out more than they have themselves, and nobody can take away their own right to manage the server's permissions.

Switching custom permissions off again puts the defaults back in charge straight away. Your rules are kept, unused, and apply again when you switch it back on.

How KanbanCord decides

Every time someone does something, KanbanCord answers one question: may this person do this, here?

  1. Administrators and the server owner may do everything. Nothing else is checked.
  2. Open permissions, if the server has them on: everyone who can view channels and send messages may work with boards, columns, labels and tasks, whatever the rules say. Managing the server, board permissions, deleting or archiving boards and the audit log still go by the rules.
  3. Otherwise, the rules are read in eight steps. Each step that has a rule for this person and this action replaces the answer so far, so the last step with a matching rule decides:
    1. Server-wide rules for Discord permissions (the defaults)
    2. Server-wide rules for @everyone
    3. Server-wide rules for roles
    4. Server-wide rules for the person
    5. The board's rules for Discord permissions
    6. The board's rules for @everyone
    7. The board's rules for roles
    8. The board's rules for the person
  4. Within one step, a Deny beats any Allow. Someone with two roles, one allowed and one denied, is denied.
  5. If no rule matches at all, the answer is no.

So a person beats their roles, roles beat @everyone, @everyone beats Discord permissions, and a board beats the server. Note what that means for the board: any board rule outweighs every server-wide rule, even a server-wide rule for one person.

Examples

The examples use a server with these roles: @everyone (View Channels), Members (Send Messages), Mods (Manage Messages) and a few roles with no Discord permissions of their own. Sam has Members.

Just the defaults

Sam may create a task: Send Messages allows it. Sam may not edit someone else's task: nothing Sam has allows it, so the answer is no.

Two roles disagree

Server-wide, Helpers are allowed to delete tasks and On break is denied it. Sam has both. Both are role rules, in the same step, so the Deny wins: Sam may not delete tasks. @everyone is different: it has a step of its own, before the other roles, just like in Discord. Deny something to @everyone and allow it for one role, and members with that role have it.

A role rule against a Discord permission

Mods may delete tasks through Manage Messages. A server-wide rule denies deleting tasks to Trial mods. A mod who also has Trial mods may not delete tasks: role rules come after Discord permissions. It works the other way too: allow editing tasks for Artists, and every artist may edit tasks, without Manage Messages.

A Deny for a Discord permission

Deny creating tasks for everyone with View Channels, and you deny it to nearly everyone, mods included: in that step a Deny beats the Allow from Send Messages or Manage Messages. To stop one group, deny it to their role instead.

One person against their roles

On break is denied creating tasks, and Sam has On break. A rule allowing Sam personally to create tasks wins: rules for a person come after rules for roles.

A private board

On the board Staff room: deny seeing the board to everyone with View Channels, and allow it for Staff. Everyone without Staff no longer sees it, and Staff do. Even Sam, who has a server-wide rule allowing them to see boards, cannot see it: the board's rule for View Channels comes after every server-wide rule. To let Sam in, add a rule for Sam on that board.

Denied server-wide, allowed on one board

Members are denied creating tasks server-wide, and the board Suggestions allows it for Members. Sam may create tasks on Suggestions and nowhere else.

Administrators

Anyone with Administrator, and the server owner, may do everything on every board. No rule can change that, so the server can never lock out the people who run it.

Open permissions

With open permissions on, Sam may create columns and edit anyone's task even though no rule allows it, but still may not delete boards or read the audit log. Someone who cannot send messages is not included. Open permissions and custom permissions cannot be on together.

Custom permissions off

The server's own rules and every board's rules are set aside, and only the defaults apply. A board that was private is visible again to everyone with View Channels, so make sure that is what you want before switching it off.

Someone who left the server

They no longer have roles or Discord permissions here, so only rules for them personally count. With none, they may do nothing.

Check it yourself

Not sure what someone may do? Check access, in the server's settings on the website, shows it for any member: every action, allowed or denied, and the rule that decided it. Start from a member and add or remove roles to see what would change, or check a set of roles on its own. In a board's settings, the same check shows what applies on that board. Server managers can check anyone, and people who may edit a board's permissions can check anyone on that board.

In Discord

The bot uses the same rules as the website: everything a command does is checked as the person who ran it. Buttons are shown to everyone, and if you are not allowed to use one, the bot tells you when you try. Autocomplete only suggests the boards you can see.

One thing to keep in mind: a board post shows a board to everyone who can see its channel. Posting needs the right to edit the board, and you are asked first if some people there could not see it otherwise.

Keeping track

Every change, including changes to permissions and switching features on or off, is recorded in the audit log on the website, with who made it and whether it came from Discord or the website.

More guides