Team Workspaces

Once your account belongs to a Team workspace (as owner or as an invited member), a Team section appears in your sidebar.

• Owners and admins get Activity, Members, Usage, Billing and Settings.
• Builders and viewers get Settings only, as a read-only page — they can see the team's name, handle, logo and description, but not change them, and they can't see the member list, invite link or billing.

Team features follow the team's plan

A team's apps get the features of the team's plan — custom domains, making an app private, the pre-publish security scan, and so on — no matter what plan each member is personally on. A member on a free personal plan can use these on the team's apps. AI usage works differently: it follows you, not the app. While you're in a team, everything you ask the AI — in a team app or one of your own — uses your seat's credits and your team's plan (which models and effort levels you can pick), not your personal balance. The credit meter in your account menu shows your seat. If your team has no active plan yet, your own plan and credits apply as before.

Already paying for your own plan? Your subscription isn't cancelled when you join a team, so it keeps billing even though your team now covers your AI usage. cdbx tells you this on the invite page and on the Plans page, with a Manage my subscription button that opens your billing portal so you can cancel (or pause, where it's offered). On your personal apps, other things that are about the app (like custom domains) use your own plan.

One team per account

An account can be in only one team — as its owner or as a member. You can't create a team while you're in one, and nobody can add a person (by username, email invite or invite link) who is already in another team; they'll see which team they're in and that they need to leave it first.

Everything the team has made

There's no separate page for it: use your ordinary Apps and Files pages. The filter's Owner choice picks Mine, Shared with me or Whole team. Owners and admins see everything in the team there, including things nobody shared with them.

The filter's Show only choice narrows the list:

• Public: open to anyone with the link. Everyone has this one.
• Connects to something, Maker has left and Waiting for access: owners and admins only.

Owners and admins can also tick several cards and use these buttons in the bar that appears:

• Stop public sharing: takes them off the open internet. Team access stays as it is.
• Make private: not public, and no longer shared with the whole team. People added by name keep their access.
• Change owner to…: pick a Builder, an Admin or the owner. Services the old owner connected are dropped.

Members

Lists everyone in the workspace — the owner, plus every invited member and their role.

Roles:

• Admin — can edit files, change settings, manage secrets, and always sees every artifact in the workspace regardless of its own sharing setting.
• Builder — can edit files; settings and secrets stay hidden.
• Viewer — can open what is shared with them, and nothing more. Viewers are free — they don't use a paid seat. Changing a Viewer to a Builder adds a seat; changing a Builder to a Viewer frees one.

Search and filter by role to find someone in a larger team, and select multiple people at once to change their role or remove them in one action.

Owners and admins can invite someone by username or email, change anyone's role, or remove them. Removing someone updates the workspace's Stripe seat count immediately.

Inviting someone without a cdbx account yet — just enter their email. They'll get an email with a link to sign in (or create an account, if they're new) — either way, they land as a member of your workspace, not a blank personal account. Until they accept, they show up under Pending invites, where you can resend the email or revoke the invite.

Invite link — turn on a reusable link anyone can use to join at a role you choose, no email required. Regenerating the link immediately invalidates the old one.

Guests — people outside your team who need to see specific things. Add one by username or email under Guests (they need a cdbx account — anyone can make one with just their email address, no Google or GitHub needed). A guest is free and sees nothing until you add them by name to an app, deck or doc from its own Sharing settings — and never sees what you share with the whole team. Remove a guest and their access ends straight away.

Removing someone — what they made in the team stays with the team. When you choose Remove from team, you're shown how much they made and asked who takes them over (you, by default). The new owner must be a Builder, an Admin or the owner. Private items stay private, with their new owner. Two things don't carry over: services the person had connected (anything that used one is marked Needs reconnecting until its new owner sets up their own), and running agents, which are paused until the new owner has looked them over. The person's own personal work is not affected.

Sign out everywhere — from a member's menu (⋮), force their active sessions to end. Useful when someone leaves and you want their access cut immediately, not just their workspace membership removed.

Usage

Team → Usage shows what the team's seats have spent on AI. Only the team's owner and admins can see it.

• This month: how many credits the seats have used, out of their combined allowance.
• Over time: credits spent each day, over the last 7, 30 or 90 days.
• By person: each person's monthly allowance, how much they've used and what's left. People who use their own API key are marked, because nothing comes out of the team for them.
• By model and by feature: which AI models the credits went on, and what people were doing (building apps, running agents, or using cdbx from another AI tool).

Only AI used on team seats is counted, not anything people spend from a personal plan.

Activity

A record of what has happened in your team, newest first. Only the owner and admins see this page.

It covers:

• People — who was invited, joined or was removed, role changes, and guests added or removed.
• Sharing — who something was shared with, anything made public or taken off public sharing, and requests for access and how they were answered.
• Apps — things made (including through another AI tool), moved in or out of the team, published, exported, archived or deleted, plus connector and custom-domain changes.
• Team settings — changes to the team's sharing rules.

Filter by person or by kind of change, or search by an item's name. Download CSV saves what you're looking at as a spreadsheet. Activity is kept for one year.

Billing

Shows your subscription's seat count and each person's own credit allocation — every seat gets its own monthly allowance, not a shared pool, so one person running out doesn't affect anyone else. An owner or admin can raise or lower an individual's credit level, or flip a seat to BYOK (that person uses their own API key and draws nothing from the subscription). When the team's own level goes down, everyone moves to the new level and keeps the credits they already have; the next monthly top-up is at the new level.

The workspace owner can also open Manage billing to reach the Stripe customer portal for payment method changes or cancellation.

If your team doesn't have a subscription yet, this page lets the owner start one: choose the credits each seat gets per month, choose monthly or yearly, and press Start subscription. You finish paying on Stripe, and nothing is charged before then. An admin who opens this page is told that only the owner can start it.

Settings

• Name — the workspace's display name, shown wherever it appears in cdbx.
• Logo and Description — a small image (PNG, JPEG or WebP, up to 2MB) and a short blurb for your team's public pages.
• Handle — your team's address on cdbx. Every app published from the workspace lives at cdbx.ai/your-handle/app-name (and your-handle.cdbx.ai), never under an individual member's username. You pick it when you create the workspace and it must be unique across cdbx — you'll see straight away whether it's free. You can change it later; published apps move to the new address immediately and their old links stop working, so update anything you've shared or embedded.
• Sharing — three rules for the whole team, each starting at its safest choice:
  • New things start as — Private (the default), Whole team can view, or Whole team can edit. The person who makes something can still change it afterwards.
  • Members can share publicly — off by default. When off, only the owner and admins can make something open to anyone with the link.
  • Members can invite guests — off by default. When off, only the owner and admins can add a guest.
• Domain-gated login default — set once, at the workspace level: an allowed email domain (e.g. yourcompany.com) that any project in this workspace uses automatically when it turns on domain-gated login without specifying its own domain. See Sharing & Publishing for what turning it on for an individual project actually does.

Only an owner or admin can change workspace settings.

Your team (builders and viewers)

Builders and viewers don't have the Team pages in the sidebar. Instead, Your team is in the account menu (click your name at the bottom left, then Your team, or click the team's name at the top). It shows:

• your role in the team;
• your AI credits (builders): how much of this month's allowance you've used and what's left;
• how sharing works here: the team's rules, in plain words;
• who's in the team, with each person's role, and who to ask to change something.

What you make lives in the team

While you are a Builder, Admin or the owner of a team with a plan, everything you make is the team's: apps, slide decks, docs, plans and agents — including anything you create through the API or from another AI tool using the cdbx MCP server. You don't choose where it goes.

• It starts private to you, unless your team's admin has set new things to be shared with the whole team. It is never public until someone makes it so.
• Your team's owner and admins can always open it, and it stays with the team if you leave.
• Anything you made before joining the team stays yours. Move it in from its Sharing & Access settings if you want the team to have it.
• Viewers and guests don't make things in the team. What they make stays on their own account.
• A copy of something your team hasn't made public can only be made by someone who builds in the team, and the copy stays in the team.

Publishing from a team

A published app belongs to whoever owns it. For an app in a Team workspace that's the team, so its link uses the team handle no matter which member clicked Publish. Apps can't be moved between your personal account and a team (or between teams) while they're published — unpublish first, since the link would change.

Who can see what

Being in a team doesn't mean you can see everything in it. Each app, deck or doc is shared at one of three levels — View only, Can edit, Admin — with the whole team or with named people, and starts private to the person who made it. See Team sharing in Sharing & Publishing. Owners and admins are the one exception: they can always open and manage everything in the team, including private items.

To see what's been shared with you, use the filter at the top of Apps and Files → Owner: Mine, Shared with me (shared with you by name) and Whole team (everything else in the team you can see).