Team
Managing members and roles
Three roles in a workspace, plus board-level access for people who should not have the workspace at all.
A team has three roles, and they differ in what they can administer rather than in what they can make. | Role | Can do | |---|---| | **Admin** | The whole team console: people, spaces, boards, credit ceilings | | **Space admin** | The same, scoped to the spaces they run | | **Member** | Open the boards in their spaces, use the library, spend the pool, train and generate | Every member creates freely. The roles are about the account, not about permission to work, which is deliberate: a workspace where half the people cannot generate is a workspace with the wrong people in it. ## Adding somebody Invite them by email from the workspace settings. They get the whole workspace: every board, the shared library, the shared LoRAs and the credit pool. That breadth is the thing to weigh before inviting. A seat is the right call for somebody on the project for weeks and the wrong one for somebody who needs to see a single board. :::tip[The narrower alternative] A board invitation gives one person one board, as Editor or Viewer, without touching the library, the pool or anything else. For a freelancer on a single deliverable that is usually the right shape. See [sharing a board](/docs/using-plnty/boards/sharing-a-board/). ::: ## The cost of the narrower option A board invitation looks cheaper and has a consequence that shows up weeks in. A guest on a board generates against **your** credits and keeps the assets in **their own** personal library. The work leaves with them, the provenance goes with it, and the client's library has a gap where those assets should be. For anybody producing real volume, a seat is the cleaner arrangement: the credits, the assets and the record all land in one place. ## Removing somebody Removing a member revokes their access to the workspace, its boards, its library and its pool. What they made in the team workspace **stays**, because it belonged to the organisation rather than to them. That is the reason the ownership rules are worth understanding before somebody leaves rather than after. :::caution[What leaves with a guest does not come back] The reverse is also true and it is the case to watch. Assets a guest generated live in their personal workspace, so removing them from a board does not retrieve anything. If work has been produced that way and it matters, collect it before the engagement ends. ::: ## Seats A team workspace holds up to fifty. Beyond that the conversation is a different plan, and both are on [plnty.app/pricing](https://plnty.app/pricing). ## What people keep When the team is the only one somebody belongs to, it becomes their workspace outright rather than sitting beside a personal one. A personal workspace stays alongside in two cases: they belong to more than one team, or they pay for a plan of their own. See [what a workspace is](/docs/using-plnty/workspaces/what-a-workspace-is/).A team has three roles, and they differ in what they can administer rather than in what they can make.
| Role | Can do |
|---|---|
| Admin | The whole team console: people, spaces, boards, credit ceilings |
| Space admin | The same, scoped to the spaces they run |
| Member | Open the boards in their spaces, use the library, spend the pool, train and generate |
Every member creates freely. The roles are about the account, not about permission to work, which is deliberate: a workspace where half the people cannot generate is a workspace with the wrong people in it.
Adding somebody
Section titled “Adding somebody”Invite them by email from the workspace settings. They get the whole workspace: every board, the shared library, the shared LoRAs and the credit pool.
That breadth is the thing to weigh before inviting. A seat is the right call for somebody on the project for weeks and the wrong one for somebody who needs to see a single board.
The cost of the narrower option
Section titled “The cost of the narrower option”A board invitation looks cheaper and has a consequence that shows up weeks in.
A guest on a board generates against your credits and keeps the assets in their own personal library. The work leaves with them, the provenance goes with it, and the client’s library has a gap where those assets should be.
For anybody producing real volume, a seat is the cleaner arrangement: the credits, the assets and the record all land in one place.
Removing somebody
Section titled “Removing somebody”Removing a member revokes their access to the workspace, its boards, its library and its pool.
What they made in the team workspace stays, because it belonged to the organisation rather than to them. That is the reason the ownership rules are worth understanding before somebody leaves rather than after.
A team workspace holds up to fifty. Beyond that the conversation is a different plan, and both are on plnty.app/pricing.
What people keep
Section titled “What people keep”When the team is the only one somebody belongs to, it becomes their workspace outright rather than sitting beside a personal one. A personal workspace stays alongside in two cases: they belong to more than one team, or they pay for a plan of their own. See what a workspace is.