Team
Shared credit pool
One balance for everybody, spendable by any member, and a transfer route that only runs one way.
A team workspace has one credit balance and every member spends from it. Unless an admin sets a ceiling, nobody has a personal allowance, so the pool is shared in the plainest sense: one person can empty it. ## What it changes day to day The number in the top bar moves when colleagues work. A balance that dropped while you were reading is usually somebody else's video render rather than an error. More importantly, the pool can be emptied by one person. A twenty-item batch on a flagship video model is a legitimate thing to run and it can stop everybody else generating for the rest of the afternoon. :::caution[Say it before you run something big] Where no ceilings are set, nothing stands between a heavy job and a stalled team except somebody mentioning it in a channel first. ::: ## Per-member ceilings An admin can cap how many credits a member spends in a month, under **Per-Member Usage and Limits** on the Credits tab. Each person can be given a number of their own, or **Set all** applies one figure across the whole team. A member with no cap reads as **Unlimited**. **Set all** also decides what people who join later get, so setting the team to a number today means the next joiner arrives on that number rather than unlimited. A cap you gave one person individually survives that, and is not overwritten the next time somebody joins. A member who reaches their ceiling stops being able to generate and is told to contact whoever runs the account. Nothing happens to the pool, so the rest of the team carries on, and ceilings reset at the start of each calendar month. This is the alternative to the social protocol above, and it suits a large team better than a small one. A cap turns "please mention it first" into something the account enforces on its own. ## Personal to team, never back You can move credits from your own wallet into the team pool. That transfer is **one-way**: credits that go into an organisation never come back out to an individual. Send what a job needs rather than your balance. The route exists for the case it solves well: a team pool has run dry, a purchase is waiting on somebody's approval, and work is stopped. A member covering the gap from their own wallet unblocks the afternoon in a few seconds. :::note[The transfer is atomic] It moves as one operation, deducting from you and granting to the organisation together, so there is no state where the credits have left one place and not arrived at the other. ::: ## Asking rather than transferring A member who needs the pool topped up can raise it rather than paying for it personally, which notifies whoever manages the account. That is usually the right first move. Transferring your own credits solves the immediate problem and quietly makes the account's real consumption harder to see, since the spending shows up without the corresponding purchase. ## Running dry The same as anywhere else, and worth repeating because in a team it affects more people: - **Boards stay open**, editable and shared - **Everything already made stays** where it is - **Local tools carry on**: remeshing, retopology, pathtraced rendering, sculpting, Precise Trace vectorizing, the merge suite - **Only new generation stops** So an empty pool is a pause on new work rather than a locked account, and the people doing 3D preparation or assembly are not blocked at all. ## Watching it The balance sits in the top bar of every board, and the price of any run sits on that run's button before you press it. Plan prices, allowances and top-up options are on [plnty.app/pricing](https://plnty.app/pricing).A team workspace has one credit balance and every member spends from it. Unless an admin sets a ceiling, nobody has a personal allowance, so the pool is shared in the plainest sense: one person can empty it.
What it changes day to day
Section titled “What it changes day to day”The number in the top bar moves when colleagues work. A balance that dropped while you were reading is usually somebody else’s video render rather than an error.
More importantly, the pool can be emptied by one person. A twenty-item batch on a flagship video model is a legitimate thing to run and it can stop everybody else generating for the rest of the afternoon.
Per-member ceilings
Section titled “Per-member ceilings”An admin can cap how many credits a member spends in a month, under Per-Member Usage and Limits on the Credits tab. Each person can be given a number of their own, or Set all applies one figure across the whole team. A member with no cap reads as Unlimited.
Set all also decides what people who join later get, so setting the team to a number today means the next joiner arrives on that number rather than unlimited. A cap you gave one person individually survives that, and is not overwritten the next time somebody joins.
A member who reaches their ceiling stops being able to generate and is told to contact whoever runs the account. Nothing happens to the pool, so the rest of the team carries on, and ceilings reset at the start of each calendar month.
This is the alternative to the social protocol above, and it suits a large team better than a small one. A cap turns “please mention it first” into something the account enforces on its own.
Personal to team, never back
Section titled “Personal to team, never back”You can move credits from your own wallet into the team pool. That transfer is one-way: credits that go into an organisation never come back out to an individual.
Send what a job needs rather than your balance.
The route exists for the case it solves well: a team pool has run dry, a purchase is waiting on somebody’s approval, and work is stopped. A member covering the gap from their own wallet unblocks the afternoon in a few seconds.
Asking rather than transferring
Section titled “Asking rather than transferring”A member who needs the pool topped up can raise it rather than paying for it personally, which notifies whoever manages the account.
That is usually the right first move. Transferring your own credits solves the immediate problem and quietly makes the account’s real consumption harder to see, since the spending shows up without the corresponding purchase.
Running dry
Section titled “Running dry”The same as anywhere else, and worth repeating because in a team it affects more people:
- Boards stay open, editable and shared
- Everything already made stays where it is
- Local tools carry on: remeshing, retopology, pathtraced rendering, sculpting, Precise Trace vectorizing, the merge suite
- Only new generation stops
So an empty pool is a pause on new work rather than a locked account, and the people doing 3D preparation or assembly are not blocked at all.
Watching it
Section titled “Watching it”The balance sits in the top bar of every board, and the price of any run sits on that run’s button before you press it.
Plan prices, allowances and top-up options are on plnty.app/pricing.