> 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/users/end-users/end-user-portal-overview.md).
# End User Portal Overview
## Statistics
The **Statistics** page is the main dashboard of the portal. It displays the user’s [**risk level**](/application-reference/users/risk-score.md), **training scores**, overall statistics, and a summary of completed training courses and [earned diplomas](/application-reference/templates/awareness-training-diploma.md).
***
## Awareness Training Courses
The **Courses** page lists all assigned training courses, organized by their **status**.
Users can switch between **card view** and **list view** using the buttons in the top-right corner.\
Filters on the left side allow courses to be viewed by **course type**.
***
## Account Settings
The **Account Settings** page allows users to:
* Update their **phone number**
* Set their **default language**
* **Reset their password**
* Enable **two-factor authentication**
{% hint style="warning" %}
End users cannot change their **email address**. If an email address needs to be updated, the user must contact their **Lucy administrator**, who can modify the [recipient entry](/guides/quick-guides/create-your-first-campaign/campaign-setup/recipients.md).
{% 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://wiki.lucysecurity.com/application-reference/users/end-users/end-user-portal-overview.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.
