> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/admin-capabilities/compensation-cards.md).
# Rate Cards / Compensation Bands
### Overview
This guide explains how rate cards work in Agentnoon, allowing organizations to standardize salary structures based on role levels and locations.
### Uploading a Rate Card
1. Prepare your **rate card / compensation bands** as a .CSV file
2. Navigate to **Upload & Map Data** and upload the CSV.
3. Once uploaded, the data appears in a table with all attributes displayed
### Mapping Salary Attributes
1. Select the attributes that define salary (e.g., **Level** and **Country**).
2. Choose the field that updates the salary (e.g., **Salary** field).
3. This ensures that salary values are dynamically populated based on predefined attributes.
### Using Rate Cards in Scenarios
1. Inside a scenario, create a new role.
2. Open **Card Content** and enable **Rate Card**.
3. Select the **Country** and **Level** for the role (or any other fields that you have defined in your upload)
4. The salary auto-populates based on the mapped rate card values, similar to a **VLOOKUP** function.
### Organizing Rate Card Fields
1. You can Group rate card fields (e.g., **Country** and **Level**) for better organization using the Groups functionality in the Fields menu.
Rate cards help enforce structured compensation bands and prevent arbitrary salary inputs across the organization.
---
# 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.agentnoon.com/admin-capabilities/compensation-cards.md?ask=&goal=
```
`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.