> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-products/secrets-security/secrets-user-interface-guide.md).
# Secrets User Interface Guide
The **Secrets** page provides a comprehensive view of all your project(s) hidden secrets. You can reach the **Secrets** page by selecting the ***Secrets** option under the **Risks** tab.*
### Statistics
Secrets' **Statistics** view shows:
* Charts for # of issues by severity, by type and by type & severity
* A table with the issues (as well as a filter for the table)
You can use filters to select specific issues:
* By Funnel Phase (see [Prioritization Funnels](/introduction-to-xygeni/prioritization-funnels.md) )
* By severity
* By issue type
* By project (pattern)
* By issue status (open, confirmed, muted, etc)
* By tag
* etc.
In the issues table, click on an issue to view its details.
{% hint style="info" %}
Please note that **any detected secret will never be sent to Xygeni servers**. Any found secret will be obfuscated previously to be sent to Xygeni.
{% endhint %}
### Prioritization funnel
Secrets' **Prioritization funnel** view shows default Secrets funnel.
{% hint style="info" %}
See [Prioritization Funnels](/introduction-to-xygeni/prioritization-funnels.md) for further details
{% 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.xygeni.io/xygeni-products/secrets-security/secrets-user-interface-guide.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.
