10.1 — Team workspaces overview
On this page
10.1 — Team workspaces overview
A team workspace lets multiple people collaborate on the same VibeMap projects under a single subscription. Members share projects, generation budget, and billing — but each member keeps their own account, their own login, and their own audit trail.
Teams are available on the Team plan ($79/month) and Enterprise plan ($199/month).
When you need a team workspace
Use a team workspace when:
- More than one person needs to read or edit the same VibeMap project (a PM and a designer working on the same product brief, or two engineers sharing a tech-stack proposal).
- You want one bill for the whole group rather than per-seat personal subscriptions.
- You want to apply role-based controls — admins manage billing and members; members read and edit projects but don't touch billing.
Stay on a personal plan (Free / Starter / Pro) when you're working solo or your collaboration model is "I send the spec to my dev team and they implement it via their own IDE agents." Personal Pro already includes MCP and API access, so your AI coding agent can pull your spec directly without your collaborators ever needing a VibeMap login.
How teams differ from personal projects
| Aspect | Personal plans (Free / Starter / Pro) | Team plans (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 billed to the team's payment method. |
| Token budget | Each user has their own monthly token budget. | The team shares a single monthly token budget across all members. |
| Roles | Just you. | Owner, admin, and member roles with different permissions. |
| Invitations | N/A. | Email-based invitations with one-click accept; expire after 7 days. |
| Workspace context | Always personal. | A user can belong to multiple teams plus have their own personal projects. |
Roles in a team workspace
Every team member has one of three roles:
- Owner — created the team. Can do everything an admin can do, plus transfer ownership and delete the team. Cannot be removed by anyone else; ownership must be transferred first.
- Admin — can invite members, change member roles, remove members, edit team settings (name, billing), and manage projects in the workspace.
- Member — can read and edit team projects. Cannot manage members or billing.
Promote trusted teammates to admin so the workload of managing the team doesn't fall on one person. Keep most teammates as members — they get full project editing access without the billing surface area.
What stays personal even when you're on a team
Joining a team does not delete or change your personal projects. Anything you created on your own account before joining a team stays under your account. You can have both:
- Personal projects under your own Free / Starter / Pro plan
- Team projects shared with your team workspace
The workspace context determines which projects you're looking at and which budget is being consumed.
What you get on a team plan
| Tier | Price | Total tokens / mo | Auto tokens | Premium tokens | Generations / day | Seats |
|---|---|---|---|---|---|---|
| Team | $79 | 18M | 15M | 3M | Unlimited | Unlimited |
| Enterprise | $199 | 48M | 40M | 8M | Unlimited | Unlimited |
Both plans include:
- Every generation feature on the Pro plan (pages, schema, files, pseudocode, agent chat, business case, sprint planner, dependency graph)
- MCP and REST API access
- Priority support
Enterprise additionally includes:
- Claude 4 Opus — frontier reasoning model, manual-pick only
- Manual model selector UI — pick which model handles each generation type
- DPA, SSO, and dedicated support