Team workspaces overview
On this page
Team workspaces overview
A shared workspace where multiple people collaborate on the same VibeMap projects under one subscription and one budget. · Optional
Read this if more than one person needs to read or edit the same projects. If you work solo — or you hand your spec to a dev team who implement it via their own IDE agents — you can skip teams entirely and stay on a personal plan.
Team workspaces require the Team plan ($79/month) or Enterprise plan ($199/month).
When you need a team workspace
Use a team workspace when:
- More than one person edits the same project (a PM and a designer on one brief; two engineers sharing a tech-stack proposal).
- You want one bill for the group rather than per-seat personal subscriptions.
- You want role-based controls — admins manage billing and members; members edit projects without touching billing.
Stay on a personal plan (Free / Starter / Pro) when you're working solo. Personal Pro already includes MCP and REST API access, so your AI coding agent can pull your spec directly without collaborators ever needing a VibeMap login.
How teams differ from personal projects
| Aspect | Personal (Free / Starter / Pro) | Team (Team / Enterprise) |
|---|---|---|
| Project ownership | One user owns each project. | The team owns projects; every member can read and edit. |
| Billing | Per-user subscription on the owner's card. | One team subscription on the team's payment method. |
| Token budget | Each user has their own monthly budget. | All members share one monthly budget. |
| Roles | Just you. | Owner, admin, and member, with different permissions. |
| Invitations | N/A. | Email invites with one-click accept; expire after 7 days. |
| Workspace context | Always personal. | A user can belong to multiple teams plus keep personal projects. |
Roles in a team workspace
Every member holds one of three roles:
- Owner — created the team. Everything an admin can do, plus transfer ownership and delete the team. Can't be removed by anyone; ownership must be transferred first.
- Admin — invite members, change roles, remove members, edit team settings and billing, manage projects.
- Member — read and edit team projects. Can't manage members or billing.
💡 Tip: Promote a trusted teammate to admin so team-management work doesn't fall on one person. Keep most people as members — full editing access, none of the billing surface area.
What stays personal
Joining a team never touches your personal projects. You can hold both at once:
- Personal projects under your own Free / Starter / Pro plan, at
/home. - Team projects shared in the workspace, at
/team/<slug>.
The workspace context (where you've navigated) determines which projects you see and which budget is consumed.
What each team tier includes
| Tier | Price | Tokens / mo (auto + premium) | Seats | Notable additions |
|---|---|---|---|---|
| Team | $79 | 18M (15M + 3M) | Unlimited | Everything on Pro, plus shared workspaces, roles, and Claude 4 Sonnet |
| Enterprise | $199 | 48M (40M + 8M) | Unlimited | Adds Claude 4 Opus, a manual model selector, DPA, SSO, and dedicated support |
Both tiers include every generation feature on Pro (pages, schema, files, agent chat, business case, sprint planner, dependency graph), MCP + REST API access, and priority support.
⚡ Power-user hints
- Free members, full power. A teammate on the Free personal plan can run the entire pipeline on a team project using the team's budget and models. Joining a team costs the member nothing and never touches their personal allowance.
- The budget is one shared pool. If teammates burn most of the month's tokens, less is left for you — the usage number you see is the whole team's consumption, not yours.
↔ The traditional way
A team normally stitches collaboration together with a shared PM tool, a wiki, and per-seat licences for every SaaS in the stack. A team workspace collapses that into one shared source of truth for the spec, one budget, and one bill — with roles instead of ad-hoc "who can touch what" conventions.
What's next
- Managing your team → — create a team, start billing, invite and manage members.
- Joining a team → — for people accepting an invitation.
- Account and billing → — personal plans and budgets.