> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/human-security/training/results.md).

# Reading results

The Training results dashboard shows how your team is progressing, from overall completion down to each employee's details and email delivery logs.

To open it, go to `Learning` > `Training` and click the `Results` tab. The summary metrics also appear at the top of the `Library` tab.

## Summary metrics

<table><thead><tr><th width="251.61328125">Metric</th><th>What it shows</th></tr></thead><tbody><tr><td><strong>Completion rate</strong></td><td>Percentage of employees who have finished at least one lesson</td></tr><tr><td><strong>Average progress</strong></td><td>Average advancement across all employees and all themes</td></tr><tr><td><strong>Started but incomplete</strong></td><td>Employees who began training but have not yet finished a lesson</td></tr></tbody></table>

Use the `Theme` filter at the top of the results table to focus on one theme.

## Employee details

Click an employee row to open their details:

* **Training progress**: which lessons are completed, started, or not yet started, per theme
* **Email logs**: every invitation and reminder sent to that employee, with type (New lesson, Lesson reminder, Theme share, Training share) and delivery status

{% hint style="info" %}
Lessons opened from a phishing simulation (phishing-to-training) do not count in the Training progress.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/human-security/training/results.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.