Workspaces
Separate environments, keys, and teammates with workspaces
Each MeetStream account owns one workspace. A workspace has its own API keys, bots, webhooks and usage. You can also be a member of other workspaces, and you move between them with the workspace switcher. That makes workspaces the natural unit for separating environments and teams.
What’s scoped per workspace
- API keys: API keys start with
ms_. A key belongs to the workspace in which you create it (app.meetstream.ai/api-key), and it cannot access the bots of another workspace. - Bots and their artifacts: the All Bots view, recordings, and transcripts.
- Webhook endpoints: workspace webhook endpoints deliver events for that workspace’s bots.
- Usage: the Usage view reports per-workspace consumption, with per-bot API-key attribution.
The workspace switcher lives in the dashboard sidebar, and the Team page manages who has access. Owners and admins see the Team page, and they can invite admins, editors and viewers.
Using workspaces as environments
This pattern keeps staging and production separate:
- Use one account, and therefore one workspace, for each environment (for example
StagingandProduction). Invite your teammates to each workspace from the Team page. - Separate API keys per workspace, injected via your secret manager — never share keys across environments.
- Separate workspace webhook endpoints per environment, so staging events never hit production handlers.
- Within a workspace, use
custom_attributesfor finer-grained routing (per customer, per job).
Rotating and revoking keys
Keys are created and revoked on the API Keys page. Revocation is immediate — create the replacement key first, roll it out, then revoke the old one.

