> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/application-reference/dashboards.md).
# Dashboards
{% tabs %}
{% tab title="Campaign" %}
"Campaigns" is the term used to describe security awareness programs, often named after specific divisions or locations for easier identification and organization.
{% endtab %}
{% tab title="Client" %}
The term "Client" can signify a single organization or, in a multi-tenant configuration, each organization is considered a separate client.
{% hint style="info" %}
Lucy segregates all data by client, ensuring that information is organized and secured on a per-client basis.
{% endhint %}
{% endtab %}
{% tab title="Type" %}
The type indicates the campaign's components, distinguishing between attack only, attack with awareness combined, or awareness only.
Phishing -> 
Awareness -> 
Phishing and Awareness -> 
{% endtab %}
{% tab title="Untitled" %}
{% endtab %}
{% tab title="Status" %}
The current phase or condition of the campaign.
-> Before a campaign is launched
-> After a campaign has been launched
-> When a campaign has been stopped
{% endtab %}
{% tab title="Recipients" %}
The total number of recipients targeted by the campaign.
{% endtab %}
{% tab title="Started" %}
The date the campaign was started
{% endtab %}
{% tab title="Stopped" %}
The date the campaign was stopped
{% endtab %}
{% tab title="Sent" %}
The total count of emails that the campaign has successfully processed.
{% endtab %}
{% tab title="Clicked" %}
The number of recipients that clicked on the link in the email
{% endtab %}
{% tab title="Success" %}
The number of recipients successfully phished.
{% endtab %}
{% tab title="Trained" %}
The number of recipients that were successfully trained.
{% endtab %}
{% endtabs %}
{% tabs %}
{% tab title="Campaign" %}
"Campaigns" is the term used to describe security awareness programs, often named after specific divisions or locations for easier identification and organization.
{% endtab %}
{% tab title="Client" %}
The term "Client" can signify a single organization or, in a multi-tenant configuration, each organization is considered a separate client.
{% hint style="info" %}
Lucy segregates all data by client, ensuring that information is organized and secured on a per-client basis.
{% endhint %}
{% endtab %}
{% tab title="Type" %}
The type indicates the campaign's components, distinguishing between attack only, attack with awareness combined, or awareness only.
Phishing ->
Awareness ->
Phishing and Awareness ->
{% endtab %}
{% tab title="Status" %}
The current phase or condition of the campaign.
-> Before a campaign is launched
-> After a campaign has been launched
-> When a campaign has been stopped
{% endtab %}
{% tab title="Recipients" %}
The total number of recipients targeted by the campaign.
{% endtab %}
{% tab title="Started" %}
The date the campaign was started
{% endtab %}
{% tab title="Stopped" %}
The date the campaign was stopped
{% endtab %}
{% tab title="Sent" %}
The total count of emails that the campaign has successfully processed.
{% endtab %}
{% tab title="Clicked" %}
The number of recipients that clicked on the link in the email
{% endtab %}
{% tab title="Success" %}
The number of recipients successfully phished.
{% endtab %}
{% tab title="Trained" %}
The number of recipients that were successfully trained.
{% endtab %}
{% endtabs %}
Lucy provides a comprehensive overview of all campaign-related activities displayed in two dashboards.
***
### Statistical Dashboard
---
# 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://wiki.lucysecurity.com/application-reference/dashboards.md?ask=&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.
