announcing: unlimited teams on overbooked

Overview

Overbooked now supports unlimited teams. Create a team for departments, studios, brands, client orgs, or any logical unit. Each team has its own dashboard, membership, billing, and seat count.

All managed from one account.

What’s new (concise)

• Unlimited teams per account: create teams freely and name them however you need (e.g., “Design”, “Acme — Client”, “Editorial”, “Devops”).

• Per-team seat model: each new team includes 1 default seat; purchase additional seats per team when you add members.

• Instant team switching: switch contexts without logging out; team dashboards, resources, and settings load instantly.

• Per-team billing: seats, invoices, and subscriptions are tracked per team under /billing.

• Owner & admin controls: role-based access enforce team-scoped permissions.

Why this matters (clear outcomes)

• Model real org structures: departments, client workspaces, or internal squads without extra accounts.

• Control costs: teams are free to create; only paid when seats are added.

• Improve security and governance: restrict access and audits per team.

• Simplify billing: invoice per team (useful for agencies charging clients or allocating internal budgets).

Concrete examples

• Agency: Create a team per client (e.g., “Acme Co.”). Each client team has its own seats, billing, and client portal. Charge clients by exporting that team’s invoice or attaching seat costs to client invoices. This is useful because if you are working with a client that has multiple projects this approach eliminates the data-noise on your actual team’s dashboard.

• Enterprise: Create a team per department (Design, Product, Legal). Admins view spending and seat counts per department and reassign seats.

• Small business / freelancer: Use teams for separate brands or projects (e.g., “Brand A”, “Side Project”). Keep sensitive client data scoped to the right team.

How billing & seats work (examples)

• New team = 1 default seat. Adding a second member to Team X triggers a seat purchase flow for that team only.

• Example: Agency has Team “Acme” (3 seats) and Team “Beta” (1 seat). Billing shows two separate subscriptions; invoices show seat counts per team for cost allocation.

• Admins can move seats between teams from the billing UI or export CSV for chargebacks.

Admin controls & APIs

• Role-based access: Owners, admins, members. Only owners can change billing or delete teams. You can make a member Admin by changing their role’s to be ‘Manager’ in your team settings.

• Server-side enforcement: APIs return 403 when requests target teams the caller isn’t a member of.

Best practices & migration checklist

• Plan team names before creating: use clear conventions (Client — Name, Dept — Name, Project — Code).

• Start by creating teams for active client engagements or internal departments you want separated for billing or access control.

• Audit membership: remove inactive members and convert contractors to limited roles before purchasing seats.

Quick start (minutes)

• Create a team: Sidebar → Team → Add a New Team

• Invite first member (team gets 1 default seat).

• Buy seats when you need more members: Billing → Add seats.

• Switch teams: Top-left team selector → choose team.

Limits & considerations

• Teams are unlimited; seats are billed per team. Keep an eye on seat usage to avoid unexpected charges.

• Deleting a team removes its resources, export important data before deletion.

Next steps

Create a pilot team for one client or department and invite 1–2 teammates to validate workflows and billing.

Contact support@overbooked.app for migration help or API details.