# Staffs
This category is divided into two main subsections: "Staff Actions" and "Staff Statistics". These two sections provide an overview of moderation activities as well as staff members' performance.
Staff Actions. The "Staff Actions" subsection provides a detailed view of the sanctions applied by all moderators on the server. These sanctions are presented in an interactive table format, with multiple columns to make it easier to read and organize the data. The columns include: Date, this column indicates the exact date the sanction was applied, allowing you to track recent or old events. Server Name, displays the name of the server on which the sanction was applied, ideal for multi-instance servers. Sanction, presents the type of sanction imposed, for example a rating, a recommendation, a Warn, a Kick, or a ban. Player, contains the nickname of the player who received the sanction. Staff, mentions the nickname of the staff member who applied the sanction, thus providing traceability of the actions taken. Reason, explains the reason for the sanction, giving a clear context for each measure applied.
Staff Statistics. The "Staff Statistics" subsection is dedicated to analyzing the performance and activity of moderation members. You will find key indicators such as: The total number of sanctions applied by each staff member, grouped by type (Notes, Recommendations, Warn, Kick, Ban). The distribution of actions over a given period, for example the last 7 days. A ranking of the most active staff members, based on their contribution to moderation, allowing to identify those who actively participate and those who are less involved. These statistics provide a clear and quantifiable overview of moderator engagement, helping managers to evaluate and adjust their team if necessary.
## Staff actions
Staff Actions. These staff actions (sanctions) are presented in an interactive table format (as below), with multiple columns to make it easier to read and organize the data. Columns include: Date, this column shows the exact date the sanction was applied, allowing you to track recent or past events. Server Name, displays the name of the server on which the sanction was applied, ideal for multi-instance servers. Sanction, shows the type of sanction imposed, such as a rating, a recommendation, a Warn, a Kick, or a ban. Player, contains the nickname of the player who received the sanction. Staff, mentions the nickname of the staff member who applied the sanction, thus providing traceability of the actions taken. Reason, explains the reason for the sanction, giving clear context for each measure applied.
Sort by sanction type. It is possible to filter the sanctions displayed by selecting a specific type via a menu at the top of the page. The available options are: All sanctions: Displays all recorded sanctions. Notes: Limits the display to only annotations added to profiles. Recommendations: Shows only recommendations added. Warn: Shows only warnings given to players. Kick: Only concerns temporary expulsions of players. Ban: Only shows cases of bans, whether temporary or permanent.
## Staffs statistics
The Staff Statistics section is divided into two main subsections, designed to provide a detailed and organized analysis of the activity of the moderation team members. These two subsections include:
A summary of the last 7 days: This section presents a condensed view of the moderation actions carried out by staff members over the last seven days, allowing you to visualize their recent activity and their involvement on the server.
Global statistics: This more comprehensive subsection groups together all the actions carried out by the staff since the beginning of their activity on the server, offering a long-term vision of their performance and their contribution to the management of the community.
This information is presented in the form of structured and clear tables, each comprising several columns intended to detail the different aspects of the staff members' activity. The columns include:
* Staffs: This column lists the names or pseudonyms of the moderators, allowing for immediate identification of each moderator involved.
* All sanctions: Indicates the total number of sanctions applied by each staff, all types combined, whether they are notes, recommendations, warnings, expulsions or bans.
* Notes: Specifies the number of notes added by the staff member, these annotations can be used to record specific information or remarks about players.
* Recommendations: Shows how many recommendations have been issued by the moderator, these recommendations notably contribute to the players' trust score.
* Warn: Reports the number of warnings given, a key indicator of the staff's preventive activity.
* Kick: Displays the total number of expulsions carried out, allowing to measure the intervention on temporary problematic behaviors.
* Ban: Lists the number of bans applied, whether temporary or permanent, an indicator of the most severe disciplinary decisions.
## 📊 Reports Statistics
The web dashboard provides server administrators with a **complete overview of all reports** submitted on the server. This statistics panel is designed to help staff teams monitor their activity, identify trends, and optimize their response efficiency.
***
### 🖥️ Accessing the Dashboard
The statistics panel is accessible from the **web administration dashboard**. Navigate to the **Staff Management** section, then open the **Report Statistics** tab.
The page is divided into **four main sections**: Global Statistics, Complete Statistics, Last Week Statistics, and a Recent Tickets log.
***
### 📈 Global Statistics
The **Global Statistics** table gives a high-level overview per server. Each row represents a server and displays the following columns:
| Column | Description |
| -------------------- | ------------------------------------------------------------------- |
| **Servers** | The name of the server |
| **T. / Month** | Average number of reports per month |
| **T. / Week** | Average number of reports per week |
| **T. / Day** | Average number of reports per day |
| **T. / Staff** | Average number of reports handled per staff member |
| **Average Duration** | Average time a report stays open before being closed |
| **Reaction Time** | Average time before a staff member takes charge of a report |
| **% Quick Reports** | Percentage of reports submitted as quick reports vs. custom reports |
> 💡 This table is **sortable by column** and includes a search field to filter results.
***
### 👥 Complete Statistics
The **Complete Statistics** table breaks down report activity **per staff member** across all time. Each row represents a staff member and includes:
| Column | Description |
| -------------------- | ----------------------------------------------------------- |
| **Staff** | Staff member's username |
| **T. Completed** | Total number of reports handled since the beginning |
| **T. / Month** | Average reports handled per month |
| **T. / Week** | Average reports handled per week |
| **T. / Day** | Average reports handled per day |
| **T. / Day Present** | Average reports handled per day the staff member was active |
| **Average Duration** | Average time spent per report |
| **Reaction Time** | Average time before taking charge of a report |
> 💡 This table is **sortable by column** and includes a search field. It supports **pagination** to browse through all staff members.
***
### 📅 Last Week Statistics
The **Last Week Statistics** table focuses on the **previous week's activity** per staff member. It uses the same columns as the Complete Statistics table but is scoped to last week only, making it ideal for **weekly team reviews**.
***
### 📆 Weekly History
Below the last week table, the **Weekly History** table displays a **week-by-week breakdown** of each staff member's report activity. Each column represents a date range (e.g. `23/03/2026 → 05/04/2026`) and shows the number of reports handled that week.
The evolution indicators use **color-coded arrows** to highlight trends:
| Indicator | Meaning |
| --------- | ---------------------------------------- |
| 🟢 `↑ +X` | Increase compared to the previous period |
| 🔴 `↓ -X` | Decrease compared to the previous period |
| — | No activity or no change |
> 💡 This view is particularly useful for identifying **inactive periods** or **sudden spikes** in a staff member's activity over time.
***
### 🎫 Recent Tickets
At the bottom of the page, the **Recent Tickets** table lists the latest reports submitted across all servers, ordered from most recent to oldest. For each ticket, the following information is displayed:
| Column | Description |
| ---------------------- | --------------------------------------------------------------- |
| **#** | Unique report ID (auto-incremented) |
| **Name** | The message or subject of the report as submitted by the player |
| **Date / Time** | Exact timestamp of when the report was submitted |
| **Opened By** | The player who submitted the report |
| **Taken In Charge By** | The staff member who picked up the report |
| **Closed By** | The staff member who closed the report |
| **Duration** | Total time the report was open |
> 💡 This table supports **pagination** and a **search field** to quickly find a specific report by name, player, or staff member.
***
> 💡 **Tip:** Use the **Weekly History** table combined with the **Global Statistics** to generate accurate weekly reports for your moderation team and identify which servers or staff members need attention.
***
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://documentation.madonnestudio.com/paid-scripts/madonnadmin/how-to-use-it/web-dashboard/staffs.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
