> 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/settings/benchmark-sectors.md).
# Benchmark Sectors
{% hint style="info" %}
Navigate to **Settings -> Benchmark Sectors**.
{% endhint %}
## Key Points About Benchmarks
* **Internal Database:** Benchmarks use an internal database, and **no data is ever submitted to our server**.
* **Anonymous Data Submission:** When using LUCY for the first time, you will be asked once if you want to submit anonymous data. The default option is **no submission of anonymous data**. Your choice is stored in the **Advanced Settings**.
By default, the **Industry** field is empty. The more tests you perform, the easier it will be to compare results in the future if you assign a Benchmark to each test.
{% hint style="info" %}
Benchmark results are **not shared** among LUCY installations. No campaign data will ever be transmitted to external servers.
{% endhint %}
***
## Using Benchmarks
You can set a **Benchmark** for a campaign when starting it. Benchmarks allow you to compare results across different campaigns and sectors, especially useful if you use LUCY to perform phishing campaigns for multiple clients.
To assign a benchmark simply select an **Industry** option when creating the campaign. You can also assign this to existing campaigns under the **Base Settings.**
***
## Editing Benchmark Values
Select a sector to edit its name, or click the trash icon under **Actions** to delete the sector.\
To create a new Sector select **+ New** in the top-right corner.
---
# 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/settings/benchmark-sectors.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.
