> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/consumption-pools/pool-members.md).
# Pool Members
Members are the licenses (for license-typed pools) or product features (for feature-typed pools) that draw from a pool's quota.
### Linking Members to a Pool
There are two ways to link a member.
#### From the Pool
On the pool detail page, the members table has an **Add licenses** or **Add features** button. The picker shows eligible consumption-type candidates for the account. Typing in the search field queries the full account by license key, so members beyond the first page of results are reachable.
Candidates already in this pool are hidden from the list. If a candidate belongs to a different pool, a badge indicates this, and selecting it shows a **"Will be moved out of …"** warning, confirming moves that member to the current pool.
#### From the License or Feature
The license edit form (for consumption-type licenses) and the product feature edit popup both include a **Consumption pool** selector. Typing searches the account's pools by name. Only pools of the matching type that belong to the same customer account appear.
Once a member is linked, its edit form displays the pool-governed settings overages, negative consumptions, and reset as read-only fields, with a note indicating these are controlled by the pool and a link to open it directly
### The Members Table
The members table on the pool detail page shows the following per member:
* **Identification**: License key, or feature name alongside its parent license
* **Customer**
* **Product**
* **Consumed:** The member's contribution and its share of the pool total, shown with a proportional bar
* **Own cap:** The member's individual `max_consumptions`
* **Held offline:** Units currently reserved by that member's offline devices (this column appears when the pool has open offline checkouts)
### Removing a Member
Click **Remove** on a member row to unlink it from the pool.
{% hint style="info" %}
Removing a member does not debit the pool and does not modify the member's counter. The member returns to standalone metering, retains its own `total_consumptions`, and its own overage, negative consumption, and reset settings take effect again immediately.
{% endhint %}
### Resetting a Single Member
Resetting a pooled member's consumption works differently from resetting a standalone license or feature.
{% hint style="info" %}
A manual reset of a pooled member returns its consumed units to the pool. The member's counter is zeroed and the pool's balance is reduced by the same amount in a single transaction. The confirmation dialog makes this explicit, for example: *"Its 500 consumed units will be returned to pool 'AI Credits'."*
{% endhint %}
The same applies when the Management API reduces a pooled member's `total_consumptions` directly, the difference is returned to the pool.
### Where Pooled Members Appear Elsewhere
**Licenses list:** An optional **Consumption pool** column shows which pool each license belongs to. Enable it under **Table columns** and it persists across sessions.
**License detail page:** A pooled license shows its pool in the license details section, the member's contribution counter, and a depleted-pool warning banner when the pool has no quota remaining.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.licensespring.com/consumption-pools/pool-members.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
