> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/cloud-cost-management/cost-governance/user-budgets/manage-user-budgets.md).

# Create and manage user budgets

Create per-user AI spending budgets, configure approval tiers and enforcement rules, monitor usage across your team, and handle limit increase requests.

***

## What you will learn from this topic

* How to create a user budget and configure its scope, period, and spending limit
* How to set up approval tiers so users can request limit increases
* How to configure notification and block enforcement rules
* How to monitor spend and user health across your team
* How to review and approve limit increase requests

***

## Before you begin

* Harness Cloud & AI Cost Management must be enabled on your account.
* The users you want to budget must belong to a Harness user group. Go to [Create a user group](#create-a-user-group) if you need to set one up.
* Make sure budget enforcement is enabled on the connector. Select **AI Governance** on your AWS connector for Amazon Bedrock, or **Enforce AI user budgets** on the provider's own connector (Cursor, Devin, GitHub Copilot, Claude Enterprise). Consult your administrator if you do not have access. Go to [Enable AI Governance on your connector](#enable-ai-governance-on-your-connector) for steps.

***

## Set up prerequisites

### Enable AI Governance on your connector

AI Governance enables Harness to enforce user budgets by capping or revoking spend on a connected provider. Enable it when you set up the connector. The steps depend on the connector type.

{% tabs %}
{% tab title="AI providers" %}
Use the following steps for Cursor, Devin, GitHub Copilot, and Claude Enterprise.

OpenAI and Anthropic Platform are not supported.

1. On the left navigation bar, under **Setup and integration**, select **Cloud Integration**, then select the **AI Providers** tab.
2. Click **+ AI Provider**, then select the provider.
3. Enter the connector details in **Overview** and click **Continue**. For Anthropic, select **Anthropic Enterprise** in the **Product Type** step. **Anthropic (Platform)** is not supported.
4. In **Connector Details**, under **Permissions**, keep **View costs (required)** selected and select **Enforce AI user budgets**.

   <figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-e62991e361ded98b7169f51748a4224bc866be26%2Fuser-budgets-ai-provider-permissions.png?alt=media" alt="Connector Details step with the Enforce AI user budgets permission selected"><figcaption><p>Select Enforce AI user budgets on the Connector Details step</p></figcaption></figure>
5. In **API Key**, select a secret that holds an administrator key with read and write access. Enforcing budgets requires write access.
6. Click **Continue**, then complete the **Connection Test**.
   {% endtab %}

{% tab title="Amazon Bedrock" %}
Amazon Bedrock is enabled on the AWS cloud connector. Harness needs an IAM policy in your AWS account to block access, so the wizard asks for the Bedrock role and policy names.

1. On the left navigation bar, under **Setup and integration**, select **Cloud Integration**, then select the **Cloud Accounts** tab.
2. Click **+ New Cloud Account**, then select **AWS**.
3. Enter the connector details in **Overview**, then complete the **Cost and Usage Report** step.
4. In **Choose Requirements**, select **AI Governance**. Harness adds the permissions to enforce AI budgets on AWS Bedrock and block access when a budget is breached.

   <figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-e97417f4de19ea1203861e0ae49ac1e02a4f73eb%2Fuser-budgets-aws-choose-requirements.png?alt=media" alt="Choose Requirements step with AI Governance selected"><figcaption><p>Select AI Governance on the Choose Requirements step</p></figcaption></figure>
5. In **AI Governance Permissions**, enter the following fields. Harness includes these values in the CloudFormation template.

   | Field                         | Description                                                                                                                                                                                                                      |
   | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | Bedrock Target Role Name      | The full name of the AWS IAM role that your Bedrock users use. For a role managed by AWS IAM Identity Center, include the `AWSReservedSSO_` prefix and the suffix, for example, `AWSReservedSSO_<permission-set-name>_<suffix>`. |
   | AI Governance IAM Policy Name | The name of the IAM policy that Harness uses to block access. The default is `harness-aicost-governance`.                                                                                                                        |

   <figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-a2ccb2f02097dd83d51dff0722e1a88803791450%2Fuser-budgets-aws-governance-permissions.png?alt=media" alt="AI Governance Permissions step with Bedrock Target Role Name and AI Governance IAM Policy Name fields"><figcaption><p>AI Governance Permissions step in the AWS connector wizard</p></figcaption></figure>
6. In **Create Cross Account Role**, click **Launch Template on AWS console** and follow the instructions to create the cross-account role. Harness prefills the **External ID**.
7. Enter the **Cross Account Role ARN**, click **Save and Continue**, then complete the **Connection Test**.

{% hint style="warning" %}
**Attach the policy for IAM Identity Center roles**

Harness cannot automatically attach the governance policy to a Bedrock target role that AWS IAM Identity Center manages. The CloudFormation stack still creates the policy, but you must attach it yourself:

1. In IAM Identity Center, open the permission set for the role.
2. Add `harness-aicost-governance` as a customer managed policy.
3. Re-provision the permission set to your AWS accounts.

Until you attach the policy, Harness cannot block users on Bedrock.
{% endhint %}
{% endtab %}
{% endtabs %}

### Create a user group

You can create a user group directly from the **Select user groups** field in the budget wizard, without leaving the page.

1. Click **+ Create new** to open the **Add User Group** panel.
2. Fill in the fields described in the following table.
3. Click **Add** to create the group. It appears immediately in the **Select user groups** drop-down menu.

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-291d69219185dfc50dbdcdb803e53ba73ce3acef%2Fuser-budgets-add-user-group.png?alt=media" alt="Add User Group panel"><figcaption><p>Add User Group panel opened from the budget wizard</p></figcaption></figure>

| Field         | Description                                                                                                                        |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Name          | A display name for the group. Harness auto-generates an identifier from it.                                                        |
| Users         | Click **Select** to add users from your account. Search by name or email and select one or more, then click **Select** to confirm. |
| Role Bindings | Assign a **Role** and **Resource Group** to the group. Click **+ Add** to add more role bindings.                                  |
| Metadata      | Optional description and tags for the group.                                                                                       |

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-7ef79325cd39cbf5b63679f88a665f15bc627e02%2Fuser-budgets-select-users.png?alt=media" alt="Add User Group panel with users and role bindings filled in"><figcaption><p>Add User Group panel with a user selected, a role binding configured, and a description added</p></figcaption></figure>

For full user group management, go to [Manage user groups](https://developer.harness.io/harness-platform/use-harness-platform/platform-access-control/add-user-groups).

***

## Create a user budget

1. On the left navigation bar, select **Cost Governance** > **User Budgets**.
2. Click **+ Create budget** to open the **Create a new Budget** wizard.

### Step 1: Budget setup

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-b1153c39baf01a2e1e90e371b0fe5e9f4fe555a4%2Fuser-budgets-step1-budget-setup.png?alt=media" alt="Step 1: Budget setup"><figcaption><p>Step 1: Budget setup</p></figcaption></figure>

| Field                         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Specify users to apply budget | Select **Harness user groups** to reuse an existing Harness user group.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| Select user groups            | Select one or more groups from the **Select user groups** drop-down menu. To create a new group, click **+ Create new**. Go to [Create a user group](#create-a-user-group) for steps.                                                                                                                                                                                                                                                                                                                                                                                            |
| Applies to                    | <p>Select which AI providers this budget governs. You can select all providers, a single provider, or any combination:</p><ul><li><strong>All AI spend</strong>: Every connected AI provider, including new providers you connect in the future</li><li><strong>Cursor</strong>: Spend from Cursor IDE</li><li><strong>Devin</strong>: Spend from Devin</li><li><strong>GitHub Copilot</strong>: Spend from GitHub Copilot</li><li><strong>Claude Enterprise</strong>: Spend from Claude Enterprise</li><li><strong>Amazon Bedrock</strong>: Spend from Amazon Bedrock</li></ul> |
| Budget name                   | Descriptive name for the budget (for example, `CCM Team - Cursor`)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| Folder                        | Select a folder to organize the budget. The drop-down menu lists all existing folders with a search bar to filter by name. If no folder is selected, the budget is placed in the **Default** folder.                                                                                                                                                                                                                                                                                                                                                                             |
| Budget period                 | <p>Select the billing cycle:</p><ul><li><strong>Weekly</strong></li><li><strong>Monthly</strong></li><li><strong>Quarterly</strong></li></ul><p>Spend resets at the start of each new period; unused allowance does not roll over.</p>                                                                                                                                                                                                                                                                                                                                           |
| Start date                    | Use the date picker to select the start date for the first budget period.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |

{% hint style="info" %}
To apply different limits per provider, create a separate budget for each provider.
{% endhint %}

### Step 2: Enforcements and notifications

Configure the per-user spending limit, approval workflow, and notification rules. The step has three parts: **Budget per user**, **Limit increase requests** (with optional advanced settings), and **Notification and block rules**.

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-819aa8f0fbec02adcbb6b95ca42034fd77ce1501%2Fuser-budgets-step2-overview.png?alt=media" alt="Step 2: Enforcements and notifications"><figcaption><p>Step 2: Enforcements and notifications</p></figcaption></figure>

### Budget per user

Enter the dollar amount that each user in the group can spend per period. The provider scope badge (for example, **All AI spend**) in the top-right reflects what you selected in [Step 1](#step-1-budget-setup).

### Limit increase requests

1. Enable **Allow users to request a higher limit** so users can request an increase from their profile.
2. Set up at least one approval tier to define who approves requests and the maximum amount they can approve. Each tier has the fields described in the following table.
3. Click **+ Add approval tier** to add multiple tiers.

| Field          | Description                                                                                                                                                                          |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Requests up to | The maximum amount this approver can approve. Harness sends the request to the approver whose tier ceiling matches or exceeds the requested amount.                                  |
| Approved by    | Who approves requests at this tier. Select **Auto-approve** to approve requests automatically without manual review. Otherwise, select one or more individual users or a user group. |

The ceiling of the highest tier is the maximum amount any user can request.

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-f05a338682f4b861776f6044d7bb9831f462d099%2Fuser-budgets-step2-approval-tiers.png?alt=media" alt="Approval tiers with Requests up to and Approved by fields"><figcaption><p>Configure approval tiers when limit increase requests are enabled</p></figcaption></figure>

<details>

<summary>Example: approval tiers</summary>

A user has a $125/month budget and needs more. You configure three approval tiers, and Harness sends each request to the designated approver based on the amount requested:

| Tier | Requests up to | Approved by         |
| ---- | -------------- | ------------------- |
| 1    | $250           | Team lead           |
| 2    | $500           | Engineering manager |
| 3    | $750           | VP of Engineering   |

* A request for $200 goes to the team lead (Tier 1).
* A request for $400 goes to the engineering manager (Tier 2).
* A request for $700 goes to the VP of Engineering (Tier 3).
* No user can request more than $750, the ceiling of the highest tier.

</details>

### Advanced limit increase settings (optional)

Expand **Advanced settings** to set limits on when users can request an increase and how much they can request:

| Field                                            | Description                                                                                  |
| ------------------------------------------------ | -------------------------------------------------------------------------------------------- |
| Users can request an increase once spend reaches | The percentage of their current budget a user must consume before they can submit a request. |
| Maximum increase per request                     | The largest single-request increase allowed.                                                 |

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-61d603cbd2706ab811e7e584adecbd0782b70090%2Fuser-budgets-step2-advanced-settings.png?alt=media" alt="Advanced settings expanded"><figcaption><p>Advanced settings: request threshold and maximum increase per request</p></figcaption></figure>

### Notification and block rules

1. Click **+ Add percentage threshold** to define when Harness should act.
2. Set the spend percentage in the **When spend reaches** field.
3. Select the action for the threshold:
   * Click **+ Notify** to send an email to the affected user when the threshold is crossed. You can add more recipients.
   * Click **+ Block** to revoke the user's access to the covered AI providers when the threshold is crossed.

For each threshold, you can notify the user, block their access, or both. Add multiple thresholds to trigger different actions at different spend levels.

{% hint style="info" %}
Harness automatically sends an email to the affected user when they are blocked, when they submit a limit increase request, and when they are unblocked. These emails are sent regardless of the notification thresholds configured here.
{% endhint %}

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-73cf5fb117e196143edff17adcb1a513d4914a83%2Fuser-budgets-step2-notifications.png?alt=media" alt="Notification rules configured with Notify and Block thresholds"><figcaption><p>Notify and Block configured on separate thresholds</p></figcaption></figure>

<details>

<summary>Example: notification thresholds</summary>

Two thresholds are configured on the same budget:

| When spend reaches | Action                             |
| ------------------ | ---------------------------------- |
| 90%                | Notify the affected user           |
| 100%               | Block access for the affected user |

Alternatively, enable both **Notify** and **Block** on the same threshold, for example, notify and block access at 100% in one rule.

</details>

### Save the budget

Click **Create** to save the budget.

***

## Monitor a user budget

From the User Budgets list, select a budget name to open its detail page.

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-f3ef98d6ee19343523bd87ff31c6adbfe71b451d%2Fuser-budgets-detail-page.png?alt=media" alt="Budget detail page"><figcaption><p>Budget detail page showing summary tiles, active enforcements, and per-user table</p></figcaption></figure>

### Summary tiles

| Tile                    | Description                                                                                               |
| ----------------------- | --------------------------------------------------------------------------------------------------------- |
| Budget per user         | The per-user limit, provider scope, and total number of users in the budget                               |
| Total budget for period | Sum of all users' limits for the current period, with a breakdown of OK, At risk, and Exceeded users      |
| Period-to-date spend    | Aggregate spend so far, shown as a percentage of the total budget, and how much of the period has elapsed |
| Pending Requests        | Number of outstanding limit increase requests                                                             |

The **Active Enforcements** bar lists the notification and block rules applied to this budget. Each tag displays the action and the spend threshold that triggers it. For example, **Notify at 80%** sends an email when a user reaches 80% of their limit, and **Block all access at 100%** revokes their access when they hit the cap.

### Per-user table

| Column          | Description                                                                                                                |
| --------------- | -------------------------------------------------------------------------------------------------------------------------- |
| User            | User email                                                                                                                 |
| Budget          | The user's current per-period spending limit that may be higher than the default if a previous limit increase was approved |
| Status          | **OK** (within limit), **At risk** (approaching the threshold), or **Exceeded** (over the limit)                           |
| Current spend   | Dollar amount spent and percentage of their limit, shown as a progress bar                                                 |
| Enforcements    | Active enforcement applied to this user                                                                                    |
| Request details | Details of any pending limit increase request for this user                                                                |

{% hint style="success" %}
Use the **Enforcements** and **Requests** filters above the table to narrow the view to users with active enforcements or pending requests.
{% endhint %}

***

## Review limit increase requests

Harness routes each submitted request to the approver assigned to the matching approval tier. As an approver, you can [approve directly](#approve-directly) without opening the review panel, or [review the full request details](#review-request-through-review-panel) before deciding.

### Approve directly

Use the inline buttons next to the specific user in the **Request details** column to act without reviewing the request.

* Click (✓) to approve the request.
* Click (✗) to reject the request.

{% hint style="info" %}
If you are an administrator and also listed as an approver for your own budget, you can approve your own requests.
{% endhint %}

### Review request through review panel

Click **Review all** in the **Pending Requests** tile to view all users who have submitted a limit increase request for this budget.

Alternatively, click **Review ↗** next to a specific user in the **Request details** column to go directly to their request.

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-f55ec80eb03dadbf575f99976201962cd28b63b3%2Fuser-budgets-pending-requests-inline.png?alt=media" alt="Budget detail page showing Review all and inline Review button"><figcaption><p>Review all in the Pending Requests tile and inline Review in the Request details column</p></figcaption></figure>

The review panel displays the following details for the selected request:

| Field             | Description                                                                                                                    |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Current budget    | The user's current per-period limit                                                                                            |
| WTD spend         | How much the user has spent so far this period, and the percentage of their current limit                                      |
| Requested upgrade | The transition from current to requested amount (for example, $125.00 → $130.00)                                               |
| Approve for       | The amount to approve. Defaults to the requested amount. You can change it to approve a lesser amount than the user requested. |

<figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-901ed3741bbff51888e817aef0b1caf86fe7b03a%2Fuser-budgets-review-panel-inline.png?alt=media" alt="Review panel showing request details and Approve for field"><figcaption><p>Review panel with current budget, WTD spend, requested upgrade, and Approve for field</p></figcaption></figure>

The panel also includes two tabs:

* **Request history**: Displays the user's past requests grouped by budget period.

  <figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-19f40b75e982ececf2712f35771ec74c5b53d204%2Fuser-budgets-request-details-history.png?alt=media" alt="Request details panel with Request history tab"><figcaption><p>Request history tab showing past requests by budget period</p></figcaption></figure>
* **Spend breakdown**: Displays a bar chart of the user's daily AI spend. Click **View on explorer** to open the full Cost Explorer. Use the following drop-down menus to change the view:

  * **By providers**: By providers, By models, By accounts, By model family, or By token type
  * **By days**: By days, By weeks, or By months

  <figure><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-d2933b57f6ae413c7227b6197c9935da929e79c2%2Fuser-budgets-request-details-spend.png?alt=media" alt="Request details panel with Spend breakdown tab"><figcaption><p>Spend breakdown tab showing daily AI spend by provider</p></figcaption></figure>

Take one of the following actions:

* **Approve**: confirm the amount in the **Approve for** field and approve the request.
* **Reject**: decline the request.
* **Skip for now**: defer the decision and move to the next request.

***

## Edit or delete a user budget

* On the budget detail page, click **Edit Budget** to reopen the two-step wizard and change any setting.
* Click **More** for additional options, including **Delete**.

{% hint style="danger" %}
Deleting a user budget removes all enforcement rules immediately. Users who were blocked regain access.
{% endhint %}

***

## Next steps

* Go to [Manage your AI budget](https://developer.harness.io/cloud-cost-management/cost-governance/user-budgets/manage-your-ai-budget.md) to view what users experience: how to view their spend and submit a limit increase request.

{% @harness-feedback/feedback %}
