Run enough separate workspaces and a problem shows up, not in the work itself but in the paperwork around it. A company that keeps a workspace per region or business unit finds that each one bills on its own and holds its own licenses. The separation that keeps the work tidy leaves the billing scattered.
Linked workspaces answer that with a parent and child relationship. You make one workspace the parent and link the others to it as children. The parent holds what is shared: the billing, and a single pool of screen licenses that the children draw from as they need them.
What matters most is what linking leaves alone. It changes how the group is billed and licensed, and nothing else. Each child keeps its own content, screens, and people, and the boundary between workspaces stays where it was. You are putting a shared roof over a set of workspaces, not taking down the walls between them.
So a license sitting idle in one workspace is available to another, and a group of workspaces settles on one bill instead of many, while staying as separate as before.
This is built for scale, for organizations running many workspaces that must stay apart yet be managed as one. How licenses are counted, and what a plan includes, are their own subject.