# Licenses and billing in a group


> Where the pool is visible, what a child can and cannot do, and how to find out who is holding the licenses.
## Where to look

Both the parent and its children see the pool, on the billing page: total, assigned, and available, plus a table of every workspace sharing it.

In the **parent**, the assigned count includes screens in every child, not just its own. A parent showing more assigned licenses than it has screens is normal and is the point of the arrangement.

See [The license pool](/docs/billing/licenses/the-license-pool/) for what each counter means.

## What a child can do

See the pool, and connect screens against it while licenses are available.

## What a child cannot do

Change the subscription, the plan, the screen count, or the payment method. Its billing page carries a banner saying billing, payment methods, and subscription management are handled by the parent, and there is no button.

To change anything, switch to the parent workspace.

## Running out

The pool is shared and first come, first served. There is no per-child quota and no reservation, so one region rolling out fifty screens can leave another unable to connect one.

Two consequences worth planning around. Tell the parent before a large rollout, not during it. And when the pool is full, the fix is either buying more licenses at the parent or [disabling](/docs/screens/managing/enable-and-disable/) screens somewhere, since nothing can be reallocated.

## Finding out who is holding them

The workspaces table sorts by licenses used, and **Export** gives you a CSV with each workspace's name, domain, licenses used, and its role in the group.

That export is the useful artefact when asking teams to give some back. Sorted by licenses used, it names the two workspaces holding most of them in about ten seconds, which is a better conversation than an all-round request.