> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voyantcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces

> Understanding workspaces and how they scope your API operations

## What is a workspace?

A **workspace** represents your organization or brand in Voyant. It contains all your products, bookings, customers, and settings. Each API key is tied to a single workspace, so all your API calls automatically operate within that workspace.

<Info>
  You don't need to specify a workspace in your API requests. Your API key determines which workspace you're operating in.
</Info>

## Live vs Sandbox

Workspaces come in two types:

|                 | Live                  | Sandbox                 |
| --------------- | --------------------- | ----------------------- |
| **Purpose**     | Production operations | Development and testing |
| **Rate limits** | 3,000 req/min         | 100 req/min             |
| **Payments**    | Real transactions     | Test mode only          |
| **Marketplace** | Full access           | Disabled                |

<Tip>
  Use a sandbox workspace during development to avoid affecting production data. Switch to a live workspace when you're ready to go live.
</Tip>

## Working with multiple workspaces

Common patterns for organizing workspaces:

* **Live + Sandbox**: One for production, one for testing
* **Multi-brand**: Separate workspaces for each brand (e.g., "Luxury Escapes" and "Budget Adventures")
* **Regional**: Separate workspaces by region with different currencies and tax rules
* **B2B/B2C**: Different workspaces for direct sales vs wholesale partners

Each workspace has its own:

* Products and departures
* Bookings and customers
* Tax and payment settings
* Team members and permissions
* Branding configuration

## API key scoping

Each API key is permanently tied to one workspace:

```javascript theme={null}
// This key only accesses Workspace A
const response = await fetch("https://api.voyantcloud.com/v1/products", {
  headers: { Authorization: "Bearer YOUR_API_KEY" },
})
```

To work with multiple workspaces, generate a separate API key for each one.

## Team roles

Users can have different roles per workspace:

| Role        | Capabilities                             |
| ----------- | ---------------------------------------- |
| **Admin**   | Full access including settings           |
| **Manager** | Manage products, bookings, and customers |
| **Agent**   | Create and manage bookings               |
| **Viewer**  | Read-only access                         |

## Limitations

* You cannot query across multiple workspaces in a single API call
* API keys cannot be shared between workspaces
* Moving data between workspaces requires export/import or support assistance

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/authentication">
    Generate and manage API keys
  </Card>

  <Card title="Rate limits" icon="gauge" href="/concepts/rate-limits">
    Understand request limits
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Make your first API call
  </Card>
</CardGroup>