> ## Documentation Index
> Fetch the complete documentation index at: https://docs.technified.xyz/llms.txt
> Use this file to discover all available pages before exploring further.
# Staff Management
> Roles, strikes, leaves of absence, notes, profiles, quotas, and performance.
Staff Management is your hub for your team: who they are, what they can do, and how they are performing. It covers roles, discipline, time off, notes, quotas, and performance scoring.
Open **Management > Staff Management** in the sidebar.
## Overview
Four stats sit at the top: Total Staff, Total Roles, Staff on LOA, and Active Strikes. Below them, search and filter the staff list by name, status, or role.
Each staff member's row shows their avatar, username, role, total moderation actions, duty status, strike count, active LOAs, and note count. A menu on each row lets you create an LOA, issue a strike, add a note, extend an LOA, or open the full profile.
Removing a staff member keeps their history (strikes, LOAs, notes) on file for the record.
## Staff roles
Roles define your hierarchy, what each tier can do, and which parts of the dashboard they can reach.
### Role settings
| Field | Description |
| ---------------- | ------------------------------------------------------- |
| Name | The role name, e.g. "Moderator" |
| Permission Level | A number that sets the hierarchy, higher is more senior |
| Discord Role | An optional linked Discord role |
### Section access
Each role can be given **read** (view) or **edit** (view and change) access per dashboard section: General, Applications, Appeals, Tickets, Moderation, Bindings, Staff Activity, Permissions, and Server Manager.
Staff roles with **Tickets** read or edit access are added to new ticket channels automatically. Without it, those staff cannot see tickets in Discord.
### Permission levels
Levels create a hierarchy where higher roles can manage lower ones, for example issuing strikes or editing LOAs.
| Level | Typical role |
| ----- | ---------------- |
| 10 | Trial Moderator |
| 25 | Moderator |
| 50 | Senior Moderator |
| 75 | Administrator |
| 100 | Owner or Manager |
Leave gaps between levels so you have room to add roles later. Start new staff with minimal permissions and grant more as they prove themselves.
## Strikes
Strikes are formal warnings that document performance issues or rule violations and support progressive discipline.
From a staff member's menu, choose **Issue Strike**. Add a reason, optional evidence, a severity (Minor, Moderate, or Severe), and notes. The member can be notified by DM.
Each strike records the date, who issued it, the reason, severity, evidence, and status.
If a strike was issued in error or successfully appealed, remove it with a reason. It is kept in history as removed.
A typical progression is verbal warning, then strike one, two, and three, then removal if behaviour continues.
## Leave of Absence
An LOA is approved time off. While it is active, activity requirements are paused and the member is not marked inactive.
| Field | Description |
| ---------- | ---------------------- |
| Start Date | When the leave begins |
| End Date | Expected return |
| Reason | Why they need time off |
| Notes | Any extra context |
LOAs move through statuses: Pending, Scheduled, Active, Expired, and Cancelled. You can extend an active LOA, end it early, or cancel and expire LOAs from the dashboard, which gives admins a quick view of who is away and for how long.
## Notes
Notes are private records attached to a staff profile. They are visible only to staff with the right permission and never shown to the member.
Use notes for performance observations, meeting outcomes, training progress, and positive recognition.
| Notes | Strikes |
| ------------------------- | -------------------------- |
| Informal documentation | Formal disciplinary action |
| Not visible to the member | The member is notified |
| No direct consequences | Counts toward discipline |
## Staff profile
The profile is the per-member deep dive at `…/staff/profile/[userId]`. It collects activity, moderation work, strikes, notes, LOAs, and recent in-game sessions in one place, and lets you act without retyping the member's ID.
It is built around three blocks:
* **Header** with avatar, linked Roblox account, role and tier, online status, and total activity hours.
* **Stat bar** with sessions, activity minutes, moderation actions, tickets closed, and active strikes.
* **Timeline and sidebar**: a chronological feed of everything involving the member, plus quick lists of active LOAs, recent strikes, and pinned notes.
Quick-action buttons in the header open a side sheet to add a note, issue a strike, or schedule an LOA, all scoped to that member.
## Staff quota
Quotas enforce in-game activity goals. Each quota sets how many minutes a member must be active over a period. When the period ends, anyone below the target generates a **pending action** for a Discord Administrator to approve or reject.
Quotas require at least one registered Roblox game, since minutes come from Roblox session data tracked by the Roblox integration. Members without a linked Roblox account are excluded so they are not flagged unfairly.
### Creating a quota
| Field | Description |
| ---------------------- | ------------------------------------------------------------ |
| Name | A readable label, e.g. "Moderator Weekly" |
| Required minutes | Minutes of activity needed per period |
| Period | Daily, 3 days, Weekly, Bi-weekly, or Monthly |
| Applies to staff roles | Which roles it targets, empty means all staff |
| Failure action | Issue Strike, Warn, or Notify Only |
| Strike severity | Minor, Major, or Severe, used only when the action is Strike |
Every failure action needs Administrator approval before it takes effect. You cannot have two enabled quotas targeting the same role at once.
### Pending approvals
Each missed quota lists the member, achieved versus required minutes, the period end date, and the proposed action. Only Discord Administrators can approve (which executes the action) or reject (which archives it).
Roll out a new quota with **Notify Only** for the first period. You see exactly who would be flagged without issuing any strikes, then upgrade to Strike once the numbers look right.
Staff can check their own progress any time with the `/leftquota` slash command, which returns an ephemeral progress bar and the reset time.
## Staff performance
The Performance page ranks staff by a single combined score over a selected period, the fastest way to see who is carrying the team.
The score adds points from five inputs and subtracts a strike penalty:
| Input | Counts |
| --------------------- | ------------------------------------------------ |
| Tickets resolved | Tickets the member closed |
| Moderation actions | Bans, mutes, warns, kicks across both platforms |
| Activity hours | In-game session time from the Roblox integration |
| Applications reviewed | Approvals plus rejections |
| Strike penalty | Subtracted per active strike |
A period dropdown scopes the leaderboard (7, 14, 30, or 90 days, or all time). In the Settings panel you can enable scoring and tune each weight and the strike penalty. Click a member to see a per-input breakdown and the raw counts behind their score.
Use performance as one signal, not the only one. Share the weights with your team so the rules are transparent, and review the board on the same cadence you review staff overall.
## Related
Live status, hours, and leaderboards from your Roblox games.
How in-game session tracking is collected.