Wallets

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.

​

Get started

1. Sign in to nOps.
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.

​

The allocation table

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.

​

Approvers and notifications

The Approvers column routes 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

​

Related

• Budgets
• Requests
• Set up AI seat tracking
• Explorer