Team
Working as a team
Add one person to a workspace and four things stop being yours: the library, the credits, the storage and the provenance.
Add one person to a workspace and the account behind your work changes hands. Four things that were private become collective, and each of them changes a habit. | Becomes shared | What that changes | | - | - | | The library | What anyone makes on a space's boards is visible to everyone in that space | | The credit pool | One balance, and any member can spend it | | Storage | One allowance, filled by everybody's work | | Provenance | The record survives the person who made the asset | ## The library is the one you feel first In a personal workspace your library is what you made. In a team workspace it also holds what your teammates made in the [spaces](/docs/team-spaces/spaces/) you share, and that is the difference between two people working near each other and two people working together. The practical effect is that the same reference stops being generated twice. Somebody made the studio backdrop last week, it is in the library, and it is searchable by what it looks like rather than by remembering who made it. Work on your own My boards is the exception. It stays out of your teammates' view, though team admins can see it from the team console. :::note[Team assets and personal assets do not mix] Work made in a team workspace lands in the team library and never appears in your personal one, and the same rule runs the other way. The boundary is real, which is what makes "everything in here belongs to the client" a true statement rather than a convention people have to keep. ::: ## The credit pool changes behaviour A shared balance is shared in both directions. A heavy afternoon of video renders can stop the rest of the team generating, and the only warning anybody gets is the number in the top bar. The habit worth building is saying it out loud before something expensive. Nobody is blocked from running a twenty-item batch on a flagship model, and everybody notices afterwards. ## Provenance stops being about memory In a personal workspace, "which settings made this" is a question about what you remember. In a team it is a question about somebody who may be on holiday, on another project, or gone. Every asset carries its own record, so the answer is on the file rather than in a head. That is the single biggest thing a team gets that an individual does not much need, and it is covered in [provenance for compliance](/docs/team-spaces/provenance-for-compliance/). ## What stays personal - **Your account**, login and profile - **Your personal workspace**, if you have one. When the team is the only workspace you belong to, it becomes your workspace outright - **Your chains**, which live in your own library and travel on boards rather than through a shared list - **Your AI**, the model Rothko writes with in your Prompt card's chat :::tip[Work in both] Most people keep the team workspace for client work and the personal one for experiments. Switching is a menu, and the separation means an experiment never lands in a client's library by accident. :::Add one person to a workspace and the account behind your work changes hands. Four things that were private become collective, and each of them changes a habit.
| Becomes shared | What that changes |
|---|---|
| The library | What anyone makes on a space’s boards is visible to everyone in that space |
| The credit pool | One balance, and any member can spend it |
| Storage | One allowance, filled by everybody’s work |
| Provenance | The record survives the person who made the asset |
The library is the one you feel first
Section titled “The library is the one you feel first”In a personal workspace your library is what you made. In a team workspace it also holds what your teammates made in the spaces you share, and that is the difference between two people working near each other and two people working together.
The practical effect is that the same reference stops being generated twice. Somebody made the studio backdrop last week, it is in the library, and it is searchable by what it looks like rather than by remembering who made it.
Work on your own My boards is the exception. It stays out of your teammates’ view, though team admins can see it from the team console.
The credit pool changes behaviour
Section titled “The credit pool changes behaviour”A shared balance is shared in both directions. A heavy afternoon of video renders can stop the rest of the team generating, and the only warning anybody gets is the number in the top bar.
The habit worth building is saying it out loud before something expensive. Nobody is blocked from running a twenty-item batch on a flagship model, and everybody notices afterwards.
Provenance stops being about memory
Section titled “Provenance stops being about memory”In a personal workspace, “which settings made this” is a question about what you remember. In a team it is a question about somebody who may be on holiday, on another project, or gone.
Every asset carries its own record, so the answer is on the file rather than in a head. That is the single biggest thing a team gets that an individual does not much need, and it is covered in provenance for compliance.
What stays personal
Section titled “What stays personal”- Your account, login and profile
- Your personal workspace, if you have one. When the team is the only workspace you belong to, it becomes your workspace outright
- Your chains, which live in your own library and travel on boards rather than through a shared list
- Your AI, the model Rothko writes with in your Prompt card’s chat