> For the complete documentation index, see [llms.txt](https://docs.finout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finout.io/user-guide/optimize/findings-beta/findings-list-beta.md).
# Findings List \[Beta]
The Findings page gives you a single table of every finding your active agents have raised, with controls to group, filter, and sort it down to what matters for your team.
{% hint style="info" %}
Viewing the Findings page requires enabling the AI Opt-In toggle in your account and having the **view findings** permission. Go to [Permissions List](https://docs.finout.io/settings/role-based-access-control-rbac/managing-roles/permissions-list) to view more details.
{% endhint %}
When looking at the findings table, you can see the following columns:
| Column | Description |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Name | Each finding is named using the pattern **Service-UseCase-ResourceID** — for example, `RDS-Rightsizing-25265e7eggdh76356637`. |
| Resource ID | The affected resource |
| Status | Open, In Progress, Fixed, or Dismissed |
| Potential savings | Estimated savings if the finding is resolved, calculated using your account's default cost type. |
| Agent | The agent that raised the finding |
| Service | The cloud service involved (for example, RDS, EC2) |
| Use case | The use case that flagged it (for example, Rightsizing) |
| Creation date | The first time this finding was flagged |
| Modified date | The last time this finding was updated |
### Default table sort
By default, the list is sorted by **potential savings**, highest first, so the biggest opportunities surface without any setup.
### Group by
Use **Group By** to roll finding up by:
* **Agent**
* **Use case**
* **Service**
* **Custom -** Any of your account's configured dimensions — up to 10, pulled from your MegaBill dimension configuration (excluding Virtual Tags with reallocation). \
\
Grouping by an account dimension lets you view findings in the context that matters to your team — by cost center, by environment, or by whatever dimensions your account already uses elsewhere in Finout. To learn more about findings dimensions, go to "Findings Dimensions".
### Filter and sort
Filter or sort the list by agent, status, use case, service, or any of your findings' custom configured dimensions. To learn more about these dimensions, go to "Findings Dimensions".
### Change finding status from the list
You don't need to open an finding to update it — change its status directly from the row, without leaving the list.
1. Locate the finding in the list.
2. **Click** the status field on that row.
3. **Select** the new status: Open, In Progress, Fixed, or Dismissed.
Learn more about finding statuses and lifecycle [here](https://docs.finout.io/user-guide/agentic-product-beta/issues-beta/issue-lifecycle-beta).
### FAQs
**Why is the findings page empty?** You need at least one active agent for findings to appear.
**How is potential savings calculated?** Using your account's default cost type — so the number you see here is consistent with how cost is calculated elsewhere in your account.
**Can I see findings from an inactivated detector in this list?** Only old findings that were created before the agent has been changed to inactive.
**Who can act on an finding from this list?** Viewing is available to anyone with view findings permission. Changing a finding's status requires findings edit permission — see [Permissions List](https://docs.finout.io/settings/role-based-access-control-rbac/managing-roles/permissions-list) for more details.
---
# 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.finout.io/user-guide/optimize/findings-beta/findings-list-beta.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.
