Skip to main content
A workspace is the top-level container in BundleUp. It owns:
  • Integrations, and the connections created through them
  • API keys, which can only reach that workspace’s connections
  • A client ID and a list of allowed redirect URIs for the authorization flow
  • Webhooks
  • Members and their roles
  • A plan, usage and billing
  • Request logs
Workspaces are fully isolated. A connection ID from workspace A used with an API key from workspace B is treated as not found.

​
One workspace per environment

Create a separate workspace for each environment you run, for example acme-dev, acme-staging and acme-prod. Each environment has its own workspace, with its own OAuth apps, API key and redirect URIs. This keeps:
  • Test connections out of production. Developers connecting their own accounts while testing never show up next to customer connections.
  • Keys separate. A leaked development key can’t reach production data.
  • OAuth apps separate. Many providers only allow one callback URL per app, or require review before production use. Separate apps per environment avoid both problems.
  • Logs readable. Production logs aren’t mixed with local experiments.
Integration identifiers (like github) can be the same in every workspace, so your code doesn’t change between environments. Only the API key, client ID and redirect URI do, and those belong in environment variables anyway.

​
Workspace settings

​
Deleting a workspace

Only the workspace owner can delete a workspace, from Settings → General. Deleting it removes its integrations, connections, keys and webhooks.