> For the complete documentation index, see [llms.txt](https://docs.nexos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexos.ai/workspace/settings/organization/workspace-credit-management.md).

# Workspace credit management

## Workspace credits management

[nexos.ai](http://nexos.ai) uses credits to track AI usage across your workspace and give owners a clear way to manage consumption across the team. Owners can review usage, set limits, and control how members access org shared credits from Settings → Workspace Credit Management.

### What is a credit?

A credit is the unit nexos.ai uses to measure and pay for model usage across every provider in the workspace. One credit represents the same amount of value whether a request is routed to OpenAI, Anthropic, Mistral, Kimi K3 or any other supported model, so credits give owners and members one consistent way to track usage instead of comparing separate provider-specific pricing.

***

### How workspace credits work

Your workspace uses two types of credits:

1. Seat credits, included with each member's seat.
2. Org credits pool, drawn from company-wide pool

#### Seat credits

Seat credits are included with each member’s seat and refresh at the start of each billing period. If they are not used during that period, they do not carry over.

<table data-header-hidden><thead><tr><th width="177.015625"></th><th></th></tr></thead><tbody><tr><td><strong>Included with</strong></td><td>Every member seat</td></tr><tr><td><strong>Renewal</strong></td><td>Start of every billing period</td></tr><tr><td><strong>Carry over</strong></td><td>No – unused seat credits expire at renewal</td></tr></tbody></table>

#### Organization credits pool (shared credits)

Org credits come from one company-wide shared pool. Members use seat credits first. Once those are exhausted, they can draw from the org credits pool up to their assigned usage limit. Organization admins control access by setting per-member limits.

<table data-header-hidden><thead><tr><th width="169.14453125"></th><th></th></tr></thead><tbody><tr><td><strong>Shared across</strong></td><td>Entire organization</td></tr><tr><td><strong>Used when</strong></td><td>A member has no seat credits remaining</td></tr><tr><td><strong>Carry over</strong></td><td>Yes – unused credits remain in the company's shared pool for future billing periods.</td></tr></tbody></table>

***

### Workspace Credit Management dashboard

Owners manage workspace credits from Settings → Workspace Credit Management. The dashboard displays the current billing period, three summary cards, and a per-member usage table. It also shows when the next renewal occurs and when seat credits and org credits limits reset.

#### Member limits and usage table

The Member limits and usage table lets owners monitor credit usage and manage org credits limit for individual workspace members. Owners can search for members, filter by team, select multiple members to update their limits in bulk, or configure a custom limit for an individual member from the menu.

#### How org credits limits work

* Limits don't reserve credits. Members draw from the org credits pool only after they exhaust their seat credits, and only up to their assigned org credit limit. Credits leave the pool only when they're actually used.
* When the org credits pool is empty, shared credit usage stops for everyone, regardless of individual limits.
* Per-member custom limits override the org credits limiy. Any manual per-member limit takes precedence and stays in place even when the org credits limit is later updated.

***

### What owners can do

#### Set an org credits limit

The org credits limit is a limit applied to every member who doesn't have a custom limit. When you set it, it applies to:

* Current members without a custom limit.
* New members who join the workspace.
* Automatic updates – updating the Org credits limit automatically updates all members using the default limit.

#### Set a per-member org credit limit

A custom limit overrides the org credit limit for that member. Once set, future changes to the org credit limit no longer affect them.

#### Bulk-edit limits across members

Owners can select multiple members from the table - including across filtered lists spanning multiple pages - and set an org credit limit for the whole selection in one pass, instead of editing rows one at a time.

#### Lower a member's limit

If you lower a member's limit below the amount of org credits they've already used during the current billing period, they immediately lose access to new AI requests and enter read-only mode for the rest of the billing period.

<br>

***

<details>

<summary>FAQ</summary>

**What's the difference between a limit and an allocation?**

A limit is a spending cap on org credits pool. An allocation would set aside credits just for one member. nexos.ai uses limits, so nothing leaves the pool and nothing is charged until the member actually spends.

**Can the total of member limits exceed the org credits pool available?**

Yes. Limits are ceilings, not reservations, so assigned limits can exceed the purchased org credits pool. When the pool empties, org credits usage stops.

**What happens to unused seat credits at the end of the billing period?**

They don't carry over. Seat credits refresh at the start of the next billing period.

**How does the org credits limit interact with per-member custom limits?**

The org credits limit applies to every member without a manual override, including new members who join later. Once an owner sets a custom limit for a specific member, that member is treated as an override and stops being affected by future changes to the org credits limit.

**What happens if I lower a member's custom limit below what they've already used this period?**

The member is cut off immediately and moved to read-only mode for the rest of the billing period – they can view existing content but can't send new requests. A confirmation dialog appears before the change is saved.

**How do we get more org credits?**

Org credits are purchased through nexos.ai sales. Contact your account manager to top up the pool.

</details>


---

# 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.nexos.ai/workspace/settings/organization/workspace-credit-management.md?ask=<question>&goal=<endgoal>
```

`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.