> For the complete documentation index, see [llms.txt](https://docs.opsnow.io/dev-opsnow-user-guide-v0.2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsnow.io/dev-opsnow-user-guide-v0.2/menu/finops-kpis/settings-tab.md).

# Settings Tab

## KPI Settings

This configuration process allows you to define performance goals, organize them into reusable sets (templates) tailored to different roles, and assign performance tracking responsibilities to the appropriate teams.

1. **Goals:** Set key performance indicators (KPIs) to be monitored across the organization and define the target values for each.
2. **Templates:** View KPI template collections organized by role, and add or remove KPIs within each template. For example, you can create KPI sets optimized for the responsibilities and functions of specific departments such as Engineering or Finance.
3. **Groups:** As the final step, assign KPI templates to user groups organized according to your organizational structure. This enables delegation of ownership and establishes a clear accountability framework for performance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opsnow.io/dev-opsnow-user-guide-v0.2/menu/finops-kpis/settings-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.