3
0
Fork 0
mirror of https://github.com/ZeppelinBot/Zeppelin.git synced 2025-03-19 07:20:00 +00:00
zeppelin/dashboard/src/components/docs/Permissions.vue

89 lines
3.6 KiB
Vue
Raw Normal View History

2019-07-28 18:24:32 +03:00
<template>
<div>
2019-08-22 01:22:26 +03:00
<h1 class="z-title is-1 mb-1">Permissions</h1>
<p class="mb-1">
2019-07-28 18:24:32 +03:00
Permissions in Zeppelin are simply values in plugin configuration that are checked when the command is used.
These values can be changed with overrides (see <router-link to="/docs/plugin-configuration">Plugin configuration</router-link> for more info)
and can depend on e.g. user id, role id, channel id, category id, or <strong>permission level</strong>.
</p>
2019-08-22 01:22:26 +03:00
<h2 class="z-title is-2 mt-2 mb-1">Permission levels</h2>
<p class="mb-1">
2019-07-28 18:24:32 +03:00
The simplest way to control access to bot commands and features is via permission levels.
These levels are simply a number (usually between 0 and 100), based on the user's roles or user id, that can then
be used in permission overrides. By default, several commands are "moderator only" (level 50 and up) or "admin only" (level 100 and up).
</p>
2019-08-22 01:22:26 +03:00
<p class="mb-1">
2019-07-28 18:24:32 +03:00
Additionally, having a higher permission level means that certain commands (such as !ban) can't be used against
you by users with a lower or equal permission level (so e.g. moderators can't ban each other or admins above them).
</p>
2019-08-22 01:22:26 +03:00
<p class="mb-1">
2019-07-28 18:24:32 +03:00
Permission levels are defined in the config in the <strong>levels</strong> section. For example:
</p>
<CodeBlock lang="yaml" trim="4">
# "role/user id": level
levels:
"172949857164722176": 100 # Example admin
"172950000412655616": 50 # Example mod
</CodeBlock>
2019-08-22 01:22:26 +03:00
<h2 class="z-title is-2 mt-2 mb-1">Examples</h2>
2019-07-28 18:24:32 +03:00
2019-08-22 01:22:26 +03:00
<h3 class="z-title is-3 mb-1">Basic overrides</h3>
<p class="mb-1">
2019-07-28 18:24:32 +03:00
For this example, let's assume we have a plugin called <code>cats</code> which has a command <code>!cat</code> locked behind the permission <code>can_cat</code>.
Let's say that by default, the plugin allows anyone to use <code>!cat</code>, but we want to restrict it to moderators only.
</p>
2019-08-22 01:22:26 +03:00
<p class="mb-1">
2019-07-28 18:24:32 +03:00
Here's what the configuration for this would look like:
</p>
<CodeBlock lang="yaml" trim="4">
plugins:
cats:
config:
can_cat: false # Here we set the permission false by default
overrides:
# In this override, can_cat is changed to "true" for anyone with a permission level of 50 or higher
- level: ">=50"
config:
can_cat: true
</CodeBlock>
2019-08-22 01:22:26 +03:00
<h3 class="z-title is-3 mt-2 mb-1">Replacing defaults</h3>
<p class="mb-1">
2019-07-28 18:24:32 +03:00
In this example, let's assume you don't want to use the default permission levels of 50 and 100 for mods and admins respectively.
Let's say you're using various incremental levels instead: 10, 20, 30, 40, 50...<br>
We want to make it so moderator commands are available starting at level 70.
Additionally, we'd like to reserve banning for levels 90+ only.
To do this, we need to <strong>replace</strong> the default overrides that enable moderator commands at level 50.
</p>
2019-08-22 01:22:26 +03:00
<p class="mb-1">
2019-07-28 18:24:32 +03:00
Here's what the configuration for this would look like:
</p>
<CodeBlock lang="yaml" trim="4">
plugins:
mod_actions:
=overrides: # The "=" here means "replace any defaults"
- level: ">=70"
config:
can_warn: true
can_mute: true
can_kick: true
- level: ">=90"
config:
can_ban: true
</CodeBlock>
</div>
</template>
<script>
import CodeBlock from "./CodeBlock";
export default {
components: { CodeBlock },
};
</script>