> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/extensions/cloud-tools/recommendations/view-recommendations.md).
# View Recommendations
View recommendations.
The **Overview** page of the Recommendations module is an analytics-based view that helps you understand how recommendations are associated with various parts of your infrastructure and how they are tracked (potential or completed).
All recommendations are divided into Cost Optimization, Operational Excellence, and Security.
Each tile on the **Overview** page displays how recommendations are distributed across different areas, and how advanced you are in implementing them. Additionally, under each tile, you can find information about the most impactful recommendation type.
Recommendations page
## **View all r**ecommendations
1. From the main menu of the Client Portal, navigate to **Cloud tools** > **Recommendations**.
2. Click the **Cost Optimization**, **Operational Excellence**, or **Security** tile to view the recommendation The following image shows the Cost Optimization recommendations:
Cost Optimization recommendations
3. Click the individual recommendation to view more details about that recommendation. The following image shows the Potential and Realized savings for Cost Optimization recommendations:
Potential and Realized savings for Cost Optimization recommendations
---
# 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.platform.softwareone.com/extensions/cloud-tools/recommendations/view-recommendations.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.
