Skip to main content

​
Workspaces & Environments

Workspaces provide the organizational structure for managing teams, billing, and multiple Crews across development, staging, and production environments.

​
Workspace Hierarchy

​
Workspaces

A Workspace is the top-level container that controls:
  • Billing — All usage charges roll up to the Workspace
  • Team access — Users are invited to Workspaces, not individual Crews
  • API keys — Authentication credentials are scoped to Workspaces
  • Limits — Rate limits and quotas apply at the Workspace level

​
Creating a Workspace

1

Sign Up

Create an account at app.usecrew.ai
2

Name Your Workspace

Choose a name that represents your organization or project
3

Select Plan

Choose a billing plan that matches your expected usage
4

Invite Team

Add team members with appropriate roles

​
Workspace Roles

​
Environments

Environments help you separate development, testing, and production workloads.

​
Environment Isolation

Each environment (Crew) maintains separate:
  • Agent configurations
  • Knowledge bases
  • Phone numbers and channels
  • Webhook endpoints
  • Analytics and logs
Production Crews should never share phone numbers or integrations with development or staging environments.

​
Promoting Between Environments

To promote changes from staging to production:
1

Export Configuration

Export your staging Crew’s agent and pathway configurations
2

Review Changes

Compare exported config against production
3

Import to Production

Import the validated configuration to your production Crew
4

Verify

Test key flows in production with monitoring enabled

​
Multi-Tenant Architectures

For platforms serving multiple clients:

​
Option 1: Workspace per Client

Pros: Complete isolation, separate billing, independent access control Cons: More overhead to manage

​
Option 2: Single Workspace, Crew per Client

Pros: Centralized management, shared team access Cons: Shared billing, less isolation

​
API Keys and Environments

API keys are scoped to Workspaces. For environment separation:
Create separate API keys for each environment and rotate them regularly.

​
Best Practices

  • Never test in production — Always use development or staging Crews
  • Mirror production — Keep staging as close to production as possible
  • Document changes — Track what’s promoted and when
  • Use descriptive names — Acme Corp - Production is better than prod
  • Audit access — Regularly review who has access to production

​
Next Steps

  • Knowledge Base — Populate your Crews with information
  • API Overview — Authenticate and interact programmatically
  • SSO — Enterprise identity management