Access

Team workspaces

Separate workspaces for each team or product, so keys, guardrails and spend stay with the team that owns them.

Own keys per teamOwn guardrails and BYOKUsage per workspace

What is Team workspaces?

Team workspaces are separate workspaces inside one Spro account. Each one has its own API keys, guardrails, BYOK connections, routing settings and usage. Teams can run different products or environments without mixing their keys or spend. On Spro you create a workspace from the workspace switcher, and each one has its own dashboard.

A company rarely runs one AI product. Production, staging and several internal tools each need different keys, rules and budgets. Putting them all in one workspace makes it hard to tell which team owns which cost or which key.

Workspaces solve that without a separate account per team. Settings are scoped to the workspace, so changing a guardrail in one team's workspace does not change another team's traffic.

Key features

What this feature does for your requests.

  • Create a workspace per team, product or environment
  • API keys belong to one workspace
  • Guardrails, BYOK keys and routing settings are set per workspace
  • Switch between workspaces from the sidebar

How it works

4 steps, from setup to the first request.

  1. 01

    Create a workspace

    Name it for the team, product or environment, such as support-prod.

  2. 02

    Add the team's keys

    Create API keys inside that workspace only.

  3. 03

    Set its rules

    Configure guardrails and BYOK connections for that workspace.

  4. 04

    Review its usage

    Read spend and requests for that workspace on its own dashboard.

Is it the right fit?

Specific situations where this feature helps, and where it does not.

Good fit if

  • A company runs several AI products that must not share keys or budgets
  • Production and staging need separate settings and logs
  • A team should manage its own guardrails without affecting other teams

Not a good fit if

  • One small team with one product, where a single workspace is enough
  • You need one budget across all teams. Usage is reported per workspace
  • You need different permissions for different people inside one workspace. Use roles for that

Team workspaces FAQs

Common questions about Team workspaces.

Route every AI request through SPRO.

One OpenAI-compatible API for 350+ models, with intelligent routing, 29 built-in guardrails, observability, and automatic failover.

Talk to sales