COMMUNITY PAGE
Workspaces for teams and enterprise
Blog / New Release
8 September 2026 · For teams and enterprises · 4 min read
Workspaces let one organization run separate teams under a single account, each with its own budget, its own members and its own governance.
Before workspaces, a team that needed separation had to create separate top-level accounts. One per client, or one per group of students. Funds were loaded into each account by hand and nothing carried across. Anyone running more than a handful spent real time on administration that produced nothing.
Workspaces replace that. One organization holds the account, the billing and the rules. Underneath it you create the workspaces you need, allocate credits to each, and decide who sees what.
What you can do
Allocate credits down
The organization holds the funds. Move FloTime and partner nodes credits into any workspace, and move them back out again.
Set workspace admins
Each workspace gets its own admin who manages members and work inside it, without visibility into the parent or its siblings.
Inherit governance
Verified, commercial-use and no-training rules set at the organization apply underneath. Lock the configuration so a workspace cannot loosen it.
Close one cleanly
Delete a workspace when a project ends. The remaining balance goes back to the parent in real time, not at the next billing cycle.
Who this is for
Three shapes keep coming up, and all three were doing this by hand before.
An agency running work for several clients needs each client separated, with its own budget and its own rules about which models may touch that client's material. One organization, one workspace per client.
A large team splitting by project or by department, where finance sits at the top and the spending happens below it. The parent controls the money and the model policy; the teams get on with the work.
A course with a teacher and a cohort of students, where each student or group needs their own space and cannot see anyone else's. The school is invoiced once and credits are distributed from the center.
Questions
What happens to a workspace's balance when I delete it?
It returns to the parent organization immediately. You can see it happen in the walkthrough above, between 3:34 and 4:21.
Can a workspace see the parent organization?
No. Visibility runs downward only. A workspace admin manages their own team and cannot see the parent or any sibling workspace.
Can each workspace have different model rules?
Workspaces inherit the organization's governance by default. The organization can lock that configuration so a workspace cannot loosen it.
Does the parent see what workspaces are spending?
Yes. Usage and run history roll up to the organization, which is where billing sits.
Floyo for enterprises
Workspaces are one part of a larger set. Floyo is the overseeing layer for enterprise visual production: any model, any node, real control over what runs, and clear terms on ownership.
set. Floyo is the overseeing layer for enterprise visual production: any model, any node, real control over what runs, and clear terms on ownership.Workspaces are managed from your organization settings. Talk to us if you need help mapping an existing multi-account setup onto them.
Floyo Workspaces are live for Teams and Enterprise. Separate teams under one organization, each with its own budget, members and inherited governance.