> 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/risk-score.md).
# Risk Score
## Introduction
Each [end user](/application-reference/users/end-users.md) has their own risk score based on the number of attacks they've been sent and the number of attacks they've failed. This reputation level can be leveraged in campaigns to send recipients specific attacks and trainings based on their risk score.
The formula for determining risk score is:
```
(1 - number of attacks failed / number of attacks sent) x 100
```
This number is then displayed as a percentage in the user's portal along with their reputation level:
***
## Custom ranges
Reputation level thresholds can be set by Lucy administrators under **Users > Risk Score**:
The levels shown above are the default configuration. Administrators can add or remove levels as desired and define the rating and minimum number of attacks necessary to reach that level.
{% hint style="success" %}
Up to 10 ranges can be defined.
{% endhint %}
You may also define ranges on a per-client basis:
---
# 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/risk-score.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.
