Inviting teammates requires a paid web plan (Indie Dev, Startup or Agentic Scale). Manage your team in Settings → Team.
How it works
- Owner. You own your workspace. Everything in it is your data: apps, tracked keywords, connected stores, co-founder, reports, balance and plan.
- Members. A teammate you invite joins your workspace with a role. They keep their own account and their own workspace as well.
- Switching. Members switch between workspaces they belong to. While a workspace is active, everything they do reads and writes the owner’s data and uses the owner’s plan.
Invite a teammate
- Open Settings → Team.
- Under Invite teammates, enter their email and pick a role.
- Optionally limit them to specific apps (see App access).
- Send the invite. They get an email with a link.
- They open the link and sign in with the invited email address. A different address, such as an Apple private relay address, won’t match; invite that address instead.
Sending a new invite to the same email replaces the earlier one. You can revoke a pending invite from Pending invites.
Roles
- Only the owner can invite or promote admins. Admins can manage editors and viewers.
- Owners and admins can change roles, remove members and see the Activity log of membership changes in Settings → Team.
- A member can leave a workspace at any time from Settings → Team → Leave workspace.
App access
An owner or admin can limit a member to some of the workspace’s apps. That member:- only sees data for those apps,
- gets an error when a request names any other app,
- can’t use account-wide features with no app attached, such as billing, API keys, store credentials, connected social accounts, the co-founder and usage.
When the owner’s plan ends
If the owner’s paid plan becomes inactive, every member’s seat is suspended. Suspended members can still see the workspace in their list but can’t open it. Seats come back as soon as the owner’s plan is active again.Switch workspace
Dashboard. Use the workspace switcher at the top of the sidebar. Your own workspace is always listed first. API. SendX-Workspace-Id with the workspace id:
- Use your own API key. With the header, the request runs as the workspace owner and uses the owner’s plan and credits.
- Without the header, requests run in your own account.
- Responses include
X-Workspace-IdandX-Workspace-Roleso you can confirm where you are acting.
team_workspace_list, then team_workspace_use with the id. Clients that let you set HTTP headers can send X-Workspace-Id on the MCP connection instead.
API
Uses 0 API credits. This endpoint always answers for you, even if your
X-Workspace-Id header points at a workspace you can no longer use, so you can always recover.
Errors
Device push tokens and notification preferences always stay personal: the header is ignored for them.
MCP tools
After switching, every data tool (my apps, keywords, co-founder, connections and so on) works on the selected workspace.
Workspace library (co-founder documents)
Theworkspace_* MCP tools are a different thing: they manage the co-founder’s document library, where business context, research notes and decision records are kept as markdown files. They work inside whichever team workspace is active.
These tools use 0 API credits.
business_context.md and AGENTS.md are your own documents: workspace_write only overwrites them when confirm_owner_document is true.
Related
- Prepaid Balance: who pays in a team
- Rate Limits & Credits: plan credits shared by the team
- Authentication

