Team credits

The rule: the workspace owner funds the workCopy Anchor Link

When a workspace member (or a story collaborator) generates anything, the credits come from the workspace owner's balance — members don't need their own subscription to contribute. If the owner's balance can't cover a generation, the member sees "Workspace owner has insufficient credits."

The header always shows what you can actually spend in the current workspace — your own balance in your personal workspace, or the owner-funded amount (and any limit that applies to you) in a team workspace.

Per-member spending limitsCopy Anchor Link

Owners can cap each member from the member list (Set Spending Limit):

• The limit counts everything the member spends in the workspace, including in-flight generations — a member can't blow past their cap with parallel renders.
• The member table's Credits Spent / Limit column shows each member's total spend against their limit (∞ when there's no limit), with a progress bar that turns yellow at 75% and red at 90%. Only owners and admins see this column; members and viewers can't see anyone else's spend or limit.
• No limit set means the member is bounded only by the owner's balance.

Story collaborators outside the workspaceCopy Anchor Link

People you share an individual story with also bill the story owner's workspace when they generate — the share dialog says as much. Note that per-member limits apply to workspace members; an outside collaborator is bounded by your balance, so share editing rights deliberately.

In AuteurCopy Anchor Link

Workspace collaboration is built into Auteur's approval flow: members generate and draft (billed to the workspace), but their locks stay provisional until the director — the project owner, or the workspace owner or an admin — finalizes them. Each project keeps a ledger of the credits it has spent, and only a director can change its budget cap. See Auteur.