Features

Workspaces

Organize your projects, teams, and agents into separate environments

Workspaces let you organize your OpenRouter projects into separate environments, each with its own API keys, routing defaults, guardrails, and observability. Use them to isolate teams, projects, or deployment stages (e.g. staging vs. production) under a single account.

Getting Started

Your existing OpenRouter setup is already in a Default workspace. All of your API keys, guardrails, BYOK provider keys, routing policies, presets, plugins, and observability integrations are there. If you don’t need multiple workspaces, keep working as usual; nothing changes.

For organizations, all members are automatically added to the Default workspace.

Creating a New Workspace

  1. Go to your home dashboard
  2. Click the workspace picker and select Create Workspace
  3. Name your workspace and add a description

Only organization admins can create and delete workspaces.

You can also create and manage workspaces programmatically using the management API.

What’s Scoped to Each Workspace

Each workspace has independent settings for:

  • API Keys — Every API key lives in a workspace. Members can create their own keys in any workspace they belong to. For organizations, admins can create system keys owned by the workspace rather than an individual user.
  • Guardrails — Each workspace has its own guardrail to govern API key and member activity. Workspace guardrails inherit account-level policies and can add more restrictive rules within those constraints.
  • BYOK — Bring your own provider keys per workspace, or share the same provider key across multiple workspaces.
  • Routing — Configure provider routing per workspace to optimize for cost, latency, throughput, or tool-calling quality.
  • Presets — Organize shortcuts for system prompts, model and provider configurations, and request parameters.
  • Plugins — Configure default plugin behavior for API requests in each workspace.
  • Observability — Connect different observability integrations per workspace, or send traces from all workspaces to the same platform.
  • Members — Control which team members have access to each workspace.

Account Level Settings

Some settings apply globally across all workspaces:

  • Activity & Logs — View all account activity and logs, with the option to filter by workspace.
  • Credits & Billing — Unified billing across all workspaces.
  • Organization — Manage organization members, roles, and workspace assignments.
  • Management Keys — API keys for administrative actions across all workspaces.
  • Privacy — Account-level data policies and provider/model restrictions that apply to all workspaces.
  • Preferences — Account preferences that apply to all workspaces.

Organization Permissions

  • Org admins have admin permissions across all workspaces. Only org admins can create or delete workspaces and add or remove member access.
  • Org members have member permissions in each workspace they’ve been added to. Members can belong to multiple workspaces, and their API keys in each workspace are governed by that workspace’s settings.
  • All org members automatically have member access to the Default workspace. Chatroom and Fusion usage is governed by the Default workspace’s settings.

Frequently Asked Questions

Within a workspace, members can create and manage their own API keys, and view other members and their roles. Members can belong to multiple workspaces. All org members automatically have access to the Default workspace. At the account level, members can view Activity and Logs.

Org admins have admin permissions across all workspaces: they can view and manage everything in every workspace, including API keys, guardrails, BYOK, routing, presets, plugins, observability, members, and settings. Only org admins can create or delete workspaces and control members’ access to each workspace. At the account level, org admins manage billing and credits, organization membership and roles, management API keys, and account-level data policies and allowed providers/models.

Yes. Management keys operate at the account level and can be used to perform administrative actions across all workspaces via the management API.

Workspaces inherit account-level data policies and allowed providers/models. Within those constraints, each workspace can set more granular guardrails to further restrict API key and member activity. The account-level policy is the ceiling; individual workspaces can only be more restrictive.

When a member is removed from a workspace, they lose access to it. Before removing them, you must first delete any API keys they created in that workspace. Their access to other workspaces is unaffected. Note: all org members retain access to the Default workspace as long as they remain in the org.

Yes. All chatroom and fusion usage is in the Default workspace.