Workspaces
Moving work between workspaces
Generating on somebody else's board can put the asset in your library rather than theirs, and knowing which happens decides who pays.
Generate on a board and the asset does not automatically belong to that board's workspace. It belongs to **your** workspace when you are a guest there, which is the single least obvious behaviour in the product and the one that decides who is billed for storage. ## The rule When you generate or upload on a board, Plnty asks one question: what is your relationship to the workspace that owns this board? | Your relationship | Where the asset lands | |---|---| | You own that workspace | That workspace | | You are a member of it | That workspace | | Neither, so you are a guest | **Your own personal workspace** | The third row is the surprising one. A freelancer invited to a single board on a client's workspace keeps every asset they generate, in their own library, against their own storage. It has one exception. A guest who has no personal workspace, which is the ordinary case for somebody whose only workspace is a single team, has nowhere of their own for the asset to go, so it lands in the board's workspace instead. ## The asset still appears on the board A link is written that lets the other people on the board see and use the asset even though it lives in a different workspace. From the canvas nothing looks unusual; everyone sees the image, everyone can feed it into the next tool. The difference is invisible until somebody goes looking in a library, at which point the asset is in the guest's and not the client's. :::caution[This decides who pays for storage] Guest-generated assets consume the guest's storage allowance, not the board owner's. On a long engagement with a freelancer generating heavily, their personal allowance is the one that fills up, and it is worth knowing that before it does. ::: ## Credits work the other way Credits are charged to the workspace that **owns the board**, because that is where the generation is happening. So a guest on your board spends your credits and keeps the assets in their library. Those two halves pointing in opposite directions is the thing to understand before inviting somebody as an Editor. :::note[Which is why board Editor is a real decision] Viewer costs you nothing and produces nothing. Editor spends from your pool. For a freelancer you want to keep working with, a seat in the workspace is usually the cleaner arrangement: the credits and the assets then land in the same place. ::: ## Getting an asset into another workspace deliberately There is no reassign button, and copying is the route. 1. Download it from the library 2. Switch to the other workspace 3. Drag it onto a board there That produces a new asset in the target workspace, consuming its storage. The copy carries no provenance from the original, because it arrives as an upload rather than as a generation, so it will have a description, tags and colours and no prompt or model. :::tip[Generate where it should live] The cheapest fix is upstream of the problem. If the work belongs to a client's workspace, get a seat in it and generate there, and the assets, the credits and the provenance all land in one place with no copying. :::Generate on a board and the asset does not automatically belong to that board’s workspace. It belongs to your workspace when you are a guest there, which is the single least obvious behaviour in the product and the one that decides who is billed for storage.
The rule
Section titled “The rule”When you generate or upload on a board, Plnty asks one question: what is your relationship to the workspace that owns this board?
| Your relationship | Where the asset lands |
|---|---|
| You own that workspace | That workspace |
| You are a member of it | That workspace |
| Neither, so you are a guest | Your own personal workspace |
The third row is the surprising one. A freelancer invited to a single board on a client’s workspace keeps every asset they generate, in their own library, against their own storage.
It has one exception. A guest who has no personal workspace, which is the ordinary case for somebody whose only workspace is a single team, has nowhere of their own for the asset to go, so it lands in the board’s workspace instead.
The asset still appears on the board
Section titled “The asset still appears on the board”A link is written that lets the other people on the board see and use the asset even though it lives in a different workspace. From the canvas nothing looks unusual; everyone sees the image, everyone can feed it into the next tool.
The difference is invisible until somebody goes looking in a library, at which point the asset is in the guest’s and not the client’s.
Credits work the other way
Section titled “Credits work the other way”Credits are charged to the workspace that owns the board, because that is where the generation is happening.
So a guest on your board spends your credits and keeps the assets in their library. Those two halves pointing in opposite directions is the thing to understand before inviting somebody as an Editor.
Getting an asset into another workspace deliberately
Section titled “Getting an asset into another workspace deliberately”There is no reassign button, and copying is the route.
- Download it from the library
- Switch to the other workspace
- Drag it onto a board there
That produces a new asset in the target workspace, consuming its storage. The copy carries no provenance from the original, because it arrives as an upload rather than as a generation, so it will have a description, tags and colours and no prompt or model.