# Savings Recommendations

> Review the savings LevelFour finds on your connected accounts, decide on each one, and choose which resources it covers before it runs.

Source: https://docs.levelfour.ai/savings-recommendations


Open **Savings** in the dashboard sidebar. The page lists the savings recommendations for your connected providers, with what each one saves a month and where it stands.

With more than one provider, the page opens on **All providers**, with one table for each provider that has savings. **Total Pipeline**, its statuses and the tab counts add up every provider. **Provider**, at the top of the page, narrows it to one.

## Statuses

Each tab lists one status and shows its count.

| Tab                | What it lists                                                                                                                                                |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **All**            | Every recommendation. This tab also shows the overview strip: **Total Pipeline**, **Top Opportunities**, and **Top Savers** once anyone has applied a saving |
| **Available**      | Savings found and not approved yet. The row action is **Save now**                                                                                           |
| **Pending**        | Savings approved and not applied yet. The Implementation column follows the rollout                                                                          |
| **Needs Approval** | Savings a member asked an admin to approve. Only people who can approve see this tab                                                                         |
| **Saved**          | Savings already applied. Each one also appears in [Savings Audit](/savings-audit)                                                                            |
| **Rejected**       | Savings someone rejected, with the reason they gave                                                                                                          |
| **Unavailable**    | Savings that cannot be applied right now. **Total Pipeline** leaves these out                                                                                |

A **New** chip marks a recommendation created in the last seven days. An **Updated** chip marks one that changed since it was created.

## Find what you need

* **Search services** narrows the table by service name.
* The filter takes **Savings** (show only parents or only groups) and **Implementation Method** (**Automated**, **IaC** or **Manual**).
* **Columns** shows, hides and reorders columns.
* With three or more tables on the page, each opens on 10 rows. **Rows per page** changes that, and each table keeps its own filters.
* The row menu holds **Remind me** (tomorrow, next week, in two weeks or next month), **Copy link** and **Pin for attention**. A banner at the top of the page tells you when reminders are due.

## Linked and grouped savings

Some savings change what another one is worth. A **Linked** badge marks them: the **Parent** is the one to apply first, and each dependent reads **Child of** with the parent's ID. Applying a child before its parent opens a **Linked Savings Dependency** prompt that names the saving you would give up by going out of order.

A parent that saves nothing on its own reads as what its children save, in the row and in the drawer. The page's counts leave it out, so each saving counts once.

A **Group** row gathers several savings of the same kind. Expand it to see each one.

## Open a recommendation

Select a row, or **Save now**, to open the drawer. It has three steps:

| Step               | What it holds                                                                                                       |
| ------------------ | ------------------------------------------------------------------------------------------------------------------- |
| **Recommendation** | What changes and why, the resources it covers, the risk, and the decision                                           |
| **Implementation** | What the chosen [implementation method](/savings-recommendations/implementation-methods) needs before it can run    |
| **Status & Logs**  | The rollout, step by step. See [Approvals and rollout](/savings-recommendations/approvals-and-rollout#status--logs) |

The **Recommendation** step starts with the title, a description, and **Open Resource in AWS Console**. Below them sit the service, account, region, environment and tags, then two tabs: **Change** (what will change, current against new) and **Metrics**. Further down are **Resources in this recommendation**, **Risk assessment**, **What happens during implementation**, and the **Activity** timeline.

The panel on the right shows the potential saving, the **Implementation method** list, and the action for your role. A notice at the foot of the drawer explains how savings on the resource are attributed under your LevelFour agreement.

## Accept or reject

An admin picks an implementation method and selects **Approve Savings**. [Approvals and rollout](/savings-recommendations/approvals-and-rollout) covers what happens next, and how a member asks an admin to approve instead.

To turn a saving down, select **Reject Savings** and give a reason:

* Operational or availability risk
* Strategic decision or internal priority
* Savings not applicable to the environment
* Other

**Can you tell us why?** takes an optional explanation. **Reject and Close** moves the saving to **Rejected**. An admin can still approve it later from the same drawer.

> **Note**
>
> Viewers see every recommendation but cannot approve, reject or request approval. [Members and roles](/account/members-and-roles) covers who can do what.

## Choose which resources it covers

A saving that spans several resources lists them under **Resources in this recommendation**, each with the date it was analyzed, its cost and its saving. Clear the ones you want to keep out, then select **Save changes**. The resources you cleared leave this saving, and the saving and cost are worked out again when it is applied.

You can change the selection while the saving is still available. Once someone requests approval, approves it, or it starts running, the list is read-only.

## Activity

The **Activity** timeline records everything that happens to the saving: approvals and rejections, the method someone chose, approval requests, access grants, pull requests, and whether the change applied or failed.

It is also where the team talks about it. A comment takes Markdown, `@` mentions a teammate, and accepts PNG, JPEG, GIF, WebP or PDF attachments up to 10 MB. **Seen by** lists the teammates who opened the saving. **Programmatic access** counts reads by API keys and connected apps, such as the MCP server, the FinOps Agent, the CLI or the SDKs.

## Create a task

**Create a task** in the drawer files the saving as an issue in a connected Jira project. Pick the site and project, confirm the title, and the link to the issue lands in the timeline. [Jira](/integrations/jira) covers connecting it.

## Next

* [Implementation methods](/savings-recommendations/implementation-methods) is how an approved saving reaches your cloud
* [Approvals and rollout](/savings-recommendations/approvals-and-rollout) is who approves, what runs, and how to retry
* [`l4 recommendations`](/cli/commands/recommendations) reads and decides savings from a terminal