# Team credits, shared pools and usage

> See which Nodespell credit balance pays for Team work, how a Studio shared pool works, and how owners track team credit usage, alerts and top-ups.

Source: https://docs.nodespell.com/teams/credits-and-usage/ · Last updated: 2026-11-10

Team credits in Nodespell come from one of two places. On a Studio Team, work in the Team workspace uses one shared credit pool that the owner pays for. On a Pro Team, each member uses their own personal credits. Owners of a Studio Team can see where the pool's credits go, by day and by member, and turn on alerts before it runs out.

## Which balance pays for a run?

| Where you run it                     | Balance used           |
| ------------------------------------ | ---------------------- |
| A Project in your personal workspace | Your personal credits  |
| A Project in a Pro Team              | Your personal credits  |
| A Project in a Studio Team           | The Team's shared pool |

Personal and Team credits are never combined. When a Studio pool is empty, your personal credits are not used for Team work, and when your personal credits run out, a Team's pool is not used for personal work. The credit display in the top bar names the balance in use, such as **Personal credits**, **Your credits in this team** or the Team's shared credit pool.

## How the Studio shared pool fills

A Studio plan gives a number of monthly credits per team member, combined into one shared pool. The pool refreshes each billing cycle, and monthly credits do not roll over. The owner can also buy **Team pool top-ups**, which only that Team's Projects use. See [Billing](https://docs.nodespell.com/account/billing/).

Removing a member frees their place but does not change the bill or the monthly credits unless the owner changes the plan.

## See where your team's credits go

Studio Team owners have a full usage view.

1. Open **Account Settings** > **Teams**, or choose **Members** under **Team actions** in the Team workspace.
2. Select the Team, then open the **Credit usage** tab.
3. Choose a **Range**: **This cycle**, **Last cycle** or **Last 30 days**.

| Part of the view | What it shows                                                                                        |
| ---------------- | ---------------------------------------------------------------------------------------------------- |
| Summary          | **Used**, **Available now**, and when the next monthly credits arrive.                               |
| Monthly meter    | **Monthly credits used** against the cycle's included credits, as a percentage.                      |
| Held credits     | Credits held for work in progress, which may be released when it finishes.                           |
| Pace estimate    | Whether the monthly credits will last until they renew at the current pace. Top-ups are not counted. |
| **Daily** chart  | Credits used per UTC day. Lighter bars are partial days; click a bar for its breakdown.              |
| Member breakdown | Each member's credits and **Share**, including **Former member** and **Unattributed usage** rows.    |

**View as table** switches the chart to a table, and selecting a member filters the view. **Download CSV** exports the data. The view counts credits actually deducted from the shared pool, including top-ups; personal spending is excluded and days are in UTC.

## What members see

Members of a Studio Team see their own usage in **Credit usage**: how much of the month's included credits the Team has used, **Team credits available now**, and how many credits they used this cycle. They do not see other members' usage.

On a Pro Team there is no shared pool to track. Owners see **Each member uses their own credits**, and members do not get a **Credit usage** tab.

## Turn on pool alerts

The owner of a Studio Team can turn on **Pool alerts** from the usage view. Alerts tell you when 80% of the month's included credits are used, and when no credits are available. Alerts are sent by email to your verified address and also appear in the app; without a verified email, they appear only in the app. To change them later, open **Teams** > **Credit usage** and choose **Alerts: On** or **Alerts: Off**.

## When the shared pool is empty

When a Studio pool runs out, Team runs stop until credits are added. Members see that the shared pool is empty and can choose **Ask _owner_ to top up**. The owner gets the request in the app and by email. After asking, a member must wait before asking again.

The owner can choose **Top up team credits**, which opens Team billing, or wait for the next monthly refresh.

## Frequently asked questions

### Can members top up a Studio Team's pool?

No. Only the Team owner manages Team billing and top-ups. Members can ask the owner to top up from the empty-pool notice.

### Do my personal top-ups work in a Studio Team?

No. Personal top-ups are added to your personal workspace only. Studio Team Projects use the Team's shared pool.

### Can members see how much each teammate used?

No. Only the owner sees usage by member. Members see their own usage and the shared balance.

### Why does the usage view show held credits?

Credits are held from the balance while work runs. You are charged only for completed work, and unused held credits are released.

### Are budgets or per-member limits available?

The app does not offer per-member spending limits. Owners can use **Pool alerts** and the usage view to watch spending.

## Related

- [Teams overview](https://docs.nodespell.com/teams/): Pro and Studio Teams.
- [Members and roles](https://docs.nodespell.com/teams/members-and-roles/): who can manage billing.
- [Plans and credits](https://docs.nodespell.com/account/plans-and-credits/): what credits are and what uses them.
- [Billing](https://docs.nodespell.com/account/billing/): Team billing and top-ups.
- [Team projects](https://docs.nodespell.com/teams/team-projects/): where Team runs happen.