What this is for
A team contains people, workspaces, one billing plan, and one agent list. A workspace is a place inside a team that groups artifacts and has its own access list. Use workspaces for clients, departments, projects, or private drafts without creating a separate team for each audience.
Team versus workspace
| Team | Workspace |
|---|---|
| Owns workspaces and artifacts | Contains artifacts inside one team |
| Controls plan, billing, members, roles, and agent roster | Controls which team members and agents can reach its artifacts |
| One plan covers all workspaces | Access may differ from one workspace to another |
Billing and plan limits remain team-scoped.
General and additional workspaces
Every team has a General workspace. General is the built-in workspace created with the team. It cannot be deleted. Additional workspaces can have narrower or different access. You can rename or delete them when their contents and your permissions allow it.
Creating another workspace does not automatically grant every team member or agent access to it. Review its access list before placing sensitive work there.
Where artifacts go
Creation, import, and duplication flows let you choose a destination workspace. A reachable workspace is one the current person or agent has permission to access. Connected agents use its workspace ID. When more than one workspace is available, do not assume a default.
An artifact can move between workspaces in the same team when you have sufficient access in both the source and destination. Moving changes who can reach it because the destination workspace's access list applies. For a different team, create a copy rather than treating the move as cross-team transfer.
Examples
- Keep broadly shared work in General.
- Give a client workspace only to the client-facing group and approved agents.
- Give a private planning workspace to a smaller set of team members.
- Separate departments with different agent grants while keeping one team plan.
Related pages
Questions and answers
When should I create another workspace instead of another team?
Create another workspace when the same team needs a different audience for a group of artifacts. The team's plan, billing, roles, and agent roster still apply.
Can everyone on the team see a new workspace?
Not automatically. Add only the people and agents who should reach it, then verify its access list before placing sensitive work there.
What changes when an artifact moves between workspaces?
The destination workspace's access list takes over. The artifact is not copied, and people with source access may no longer see it.