> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Wallets

> Split AI spend into groups, assign seats to them, set allocation percentages, and choose who approves each group's limit requests.

**Wallets** is where you decide how AI spend is divided. You define value groups, assign seats to them, give each group a share of the pool, and name the people who approve that group's limit requests. Everything downstream — budget targets, forecasts, request routing, rebalancing — reads from what you set here.

<Note>
  Wallets requires seat tracking admin rights. It is the first thing to finish after creating a project: [Budgets](/ai/budgets) stays locked until at least one group exists.
</Note>

## Get started

1. Sign in to [nOps](https://clara.nops.io/dashboard).
2. In the sidebar, open **AI → Wallets**.
3. Create groups that match how you actually think about AI spend — teams, products, cost centers.
4. Assign seats from **Unassigned seats** into those groups.
5. Click **Save**.

Under the hood this is an AI-category Cost Allocation showback plus a scoped Explorer report, both provisioned for you. You can open the showback directly at any time.

## Key features

### Groups or users

An allocation can be organized two ways, and the choice changes the vocabulary throughout:

* **Groups** — the usual case. You create named groups such as `Engineering` and assign seats to them.
* **Users** — each seat is its own line. There is no **Add group** button, because the users come from your seat roster.

Switch modes in project settings under **Project & budget**. Group mode is what unlocks the vendor roll-up and per-group targets in [Budgets](/ai/budgets).

### The allocation table

| Column                  | What it holds                                                             |
| ----------------------- | ------------------------------------------------------------------------- |
| **Group** (or **User**) | The value the spend is allocated to.                                      |
| **Allocation %**        | That group's share of the pool.                                           |
| **Members**             | How many seats are assigned.                                              |
| **Approvers**           | Who reviews this group's limit requests. Appears once a budget is linked. |
| **Spend**               | Actual spend for the group.                                               |

Above the table, a coverage line tells you exactly where you stand — what percent is allocated to groups and what percent is still unassigned. Use the search box to find a group, and **Add group** to create one. Creating a group does not assign anyone to it; you do that from **Unassigned seats** below.

Expand any group row to see the AI seats inside it.

### The FinOps row

The first row of the table is **FinOps** — not a spending group, but the people who should hear about everything. Its **Allocation %** cell reads **Notified only**. Expand it to pick who gets FinOps-level notifications and how often.

### Unassigned seats

Below the table, **Unassigned seats** lists every seat nOps has discovered that does not belong to a group yet. Search it, then assign seats into groups.

**Add by email** opens **Watch a seat by email**, which creates a pending seat for someone who has not shown up in provider spend yet. Assign it to a group and any spend matching that email will follow it automatically. This is how you get ahead of a new hire instead of waiting for their first invoice line.

### Scope, dates, and saving

The toolbar above the table controls what the allocation covers:

* **Scope chips** name the providers included, or read **All sources**. Edit them to narrow the allocation to specific providers.
* A **date range** selector sets the window the spend figures cover.
* **CSV** actions let you take the allocation out and bring bulk edits back.
* The **More options** menu has **Open in Cost Allocation** to work on the underlying showback directly, and **Link existing…** to point the project at a showback you already built.

<Warning>
  Scope changes are not live. Click **Save** to apply them and update the linked Explorer report. Saving also regenerates your budget's planning targets from the new allocation.
</Warning>

### Approvers and notifications

The **Approvers** column routes [Requests](/ai/requests) to the person who actually owns that group's spend, rather than sending everything to one admin. Group-level recipients are configured here; project-wide notification routing lives in project settings under **Notifications**.

If your provider supports it, you can also sync group membership from the provider rather than maintaining it by hand — Claude Enterprise supports group sync today.

## FAQs

<AccordionGroup>
  <Accordion title="What happens to spend that isn't allocated to a group?">
    It stays unallocated and shows in the coverage line as unassigned. It still counts toward total AI spend; it just is not attributed to anyone, so it cannot be budgeted or forecast per group.
  </Accordion>

  <Accordion title="Do I have to allocate 100%?">
    No, but the coverage line will keep telling you what is missing, and unassigned spend will not appear in per-group targets.
  </Accordion>

  <Accordion title="Can I use a Cost Allocation showback I already built?">
    Yes. Use **Link existing…** in the **More options** menu instead of letting the project provision a new one.
  </Accordion>

  <Accordion title="Why did my budget targets change after I saved?">
    Saving the allocation regenerates the budget's planning targets so they match the new group structure. Review them in [Budgets](/ai/budgets) after a significant reorganization.
  </Accordion>

  <Accordion title="Someone new joined and isn't listed.">
    Seats appear once the provider reports spend for them. To get ahead of that, use **Add by email** to create a pending seat and assign it now.
  </Accordion>
</AccordionGroup>

## Related

* [Budgets](/ai/budgets)
* [Requests](/ai/requests)
* [Set up AI seat tracking](/ai/setup)
* [Explorer](/inform/explorer)