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

# Workspace

> Understand workspace as a core scope concept across Forge products.

A workspace is the core organizational scope used across Forge products and APIs.

You use workspace context to separate teams, resources, and outbound operations.

## Why workspace matters

* Access control is usually evaluated at workspace level.
* Many API operations and MCP tools are workspace-scoped.
* Contacts, sequences, sender profiles, and related resources are typically managed per workspace.

## Workspace in day-to-day integrations

1. Resolve the target workspace before running writes.
2. Persist workspace IDs in your integration state.
3. Pass workspace IDs on workspace-scoped API endpoints and MCP tools.
4. Handle workspace authorization failures (for example 403) as scope errors, not transport errors.

## Common mistakes to avoid

* Reusing a workspace ID from one account in another account context.
* Assuming a valid API key can access every workspace.
* Running write operations before confirming workspace scope.

## Related resources

* [Mailbox concept](/overview/mailbox)
* [Authentication](/authentication)
* [Salesforge API authentication](/salesforge-api/api-endpoints)
* [MCP overview](/mcp/overview)