Permissions

Description

This mono-module handles the manipulation or viewing of user's permission levels. Kosaka has an entirely separate permission system for security reasons and to permit more stealthy administrative moves.
Kosaka grants automatically Kernel-Level privileges to a guild's owner upon anyone attempting to run a command that requires permissions.

🌲 Core Modules

Commands & More Details

All commands in this module follow the following authorization table:

Allowed Installs: ✔️ Guild Bot | ✖️ User Application

Allowed Places: ✔️ Guilds | ✖️ Kosaka DMs | ✖️ Private Channels

[Power]:

- Hardware (Un-selectable) | The Sirio Network Administrator, access to commands tied to Kosaka's Development.

- Server Owner (Un-selectable) | Special administrative powers, targeted at... the server's owners. (wow)

Quirk: The Server Owner permission is entirely separate and does not act like a renamed Kernel-Level permission level. Running commands that require higher privileges as the server owner while not having said Kernel-Level permission level will result in an insufficient permissions error. This is intended.

- Kernel | Near-Absolute administrative powers, targeted at trusted Administrators.

- Root | Regular administrative powers, targeted at Moderators.

- Privileged | Additional safe commands, targeted at VIPs.

- User | Basic Command access.

@Kernel+ /permissions set_user (User: User) (Power: [Power]) — Changes the permission of (User) to (Power).

Notice: Hardware-Level Users or Kosaka cannot be modified, Kernel-Level Users can only be modified by the Server Owner.

@Kernel+ /permissions set_role (Role: Role) (Power: [Power]) — Changes the permission of (Role) to (Power).

Notice: Hardware-Level Users or Kosaka cannot be modified, Kernel-Level Roles can only be modified by the Server Owner.

@Privileged /permissions info (User: User) — Returns the Power Level of a specified (User).