Staff and access

Two tiers of people: admins (manage the bot and settings) and staff (work with tickets and use the web panel). Both are set on the “Staff” tab. Nobody else gets into the web panel.

Tiers

Admins

Who: The server owner; roles with the “Administrator” permission on Lolka; roles and people from “Staff → Admins”
In chat: All setup commands, any actions in tickets
In the web panel: Everything, including server Settings

Staff

Who: Roles from “Staff → Staff” (same as /staff)
In chat: Sees all tickets except private ones (/ticket private); claiming, closing, reopening, members, priority, escalation
In the web panel: All sections except Settings; can be cut down per role (the matrix)

Tier	Who	In chat	In the web panel
Admins	The server owner; roles with the “Administrator” permission on Lolka; roles and people from “Staff → Admins”	All setup commands, any actions in tickets	Everything, including server Settings
Staff	Roles from “Staff → Staff” (same as /staff)	Sees all tickets except private ones (/ticket private); claiming, closing, reopening, members, priority, escalation	All sections except Settings; can be cut down per role (the matrix)

The owner and roles with “Administrator” on Lolka are always admins; you don’t need to add them to the list. The list is for people you don’t want to give “Administrator” on the whole server: they are admins both in the web panel and for the bot’s commands.

Roles in tickets

Server staff

Where it is set: Staff → Staff, /staff add
What it gives: All of the server's tickets + web panel access.

Category staff

Where it is set: Categories → category → Access → Support roles
What it gives: The same, but only in this category's tickets. No web panel access.

Category extra roles

Where it is set: Categories → category → Access
What it gives: See the category's ticket channels. Not staff: they don't claim, don't close, aren't in the stats.

Roles that bypass limits

Where it is set: Categories → category → Limits → Roles without a limit
What it gives: Open tickets when limits are used up. Adds no permissions inside the ticket. On top of the roles from the server settings.

Ticket author

Where it is set: —
What it gives: Writes in their ticket, can close it (or request closing). After closing they can read but not write; reopen — if the category allows it.

Role	Where it is set	What it gives
Server staff	Staff → Staff, /staff add	All of the server's tickets + web panel access.
Category staff	Categories → category → Access → Support roles	The same, but only in this category's tickets. No web panel access.
Category extra roles	Categories → category → Access	See the category's ticket channels. Not staff: they don't claim, don't close, aren't in the stats.
Roles that bypass limits	Categories → category → Limits → Roles without a limit	Open tickets when limits are used up. Adds no permissions inside the ticket. On top of the roles from the server settings.
Ticket author	—	Writes in their ticket, can close it (or request closing). After closing they can read but not write; reopen — if the category allows it.

Who counts as staff in a particular ticket

Admins+ server staff+ the ticket category's roles

A union. The “Claim”, “Close”, “Reopen” buttons and the /ticket … commands respond to this circle.

Who sees the ticket channel

staff (the circle above)+ the category's extra roles+ the author+ people added with /ticket add

A private ticket (/ticket private) is seen only by admins, the claimer, whoever made it private, the author and added members — both in the channel and in the web panel.

Web panel access

You sign in with /dashboard token in chat: admins and staff can use the command; the link works once and lives for 5 minutes. What’s open after signing in:

Overview, Statistics, Logs, Transcripts

Admins: yes
Staff: yes, always

Tickets, Categories, Panels, Commands, Staff

Admins: edit
Staff: by the matrix: edit by default, can be cut down to view or closed

Blacklist

Admins: edit
Staff: by the matrix: view by default, can be closed; only admins change it, like /blacklist in the bot

Automations

Admins: edit
Staff: by the matrix: view by default, editing can be allowed or the section closed

Server settings

Admins: yes
Staff: no

Section	Admins	Staff
Overview, Statistics, Logs, Transcripts	yes	yes, always
Tickets, Categories, Panels, Commands, Staff	edit	by the matrix: edit by default, can be cut down to view or closed
Blacklist	edit	by the matrix: view by default, can be closed; only admins change it, like /blacklist in the bot
Automations	edit	by the matrix: view by default, editing can be allowed or the section closed
Server settings	yes	no

Staff permission matrix

Staff → Staff → “Web panel sections”: for each support role and each section (Tickets, Panels, Categories, Commands, Staff, Blacklist, Automations) — a “No · Views · Edits” switch. The default is “Edits”, for “Automations” — “Views”: rules act on the whole server by themselves, so the right to change them is granted explicitly. Staff can at most view the “Blacklist”: only admins can change it, same as with the /blacklist command. Ban, kick, unban, roles and ticket access in enabled rules can be added and changed only by the owner or a Lolka administrator (staff with edit rights can still save a disabled rule), and the “Blacklist” and “Remove from blacklist” steps only by admins. A person with several roles gets the widest value. Admins aren’t limited by the matrix — otherwise you could lock yourself out of the settings.

How fast changes apply

An access decision is remembered for 20 seconds. The bot learns about roles being given or taken away right away; changes to a role’s own permissions (for example, “Administrator”) — within a minute. Saving on the “Staff” tab resets everything at once.

If there are no staff and the admin lists are empty, only the owner and roles with “Administrator” on Lolka can sign in to the web panel.

The “Staff” tab in the web panel

•Admins — roles and users by ID. Only admins can change them.
•Staff — support roles (same as /staff list) with the section matrix below them.
•Adding or removing a role changes access to already open tickets right away too.
•“What a role can do” — pick a role and see its tier, what's open to it in chat and in the web panel, and in which panels/categories it is set separately.
•The per-staff table (in progress, closed, average time) is in Statistics.