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

# Workspaces

> Create and manage workspaces to organize your SMS projects, campaigns, and developer apps with Briq's workspace system.

# Workspaces

Workspaces are containers that help you organize your SMS activities, campaigns, and developer apps. Each workspace can contain multiple campaigns and control whether developer apps can access it through the developer access setting.

## What is a Workspace?

A workspace is a logical container that holds:

* **Campaigns**: Organize your messaging campaigns
* **Developer Apps**: Control which apps can access the workspace
* **Settings**: Basic workspace configuration like name and description
* **Developer Access**: Enable or disable developer app access to this workspace

## When to Use Workspaces

### Project Organization

* **Marketing Campaigns**: Separate workspace for promotional activities
* **Transactional Messages**: Dedicated workspace for order confirmations, alerts
* **Client Projects**: Individual workspaces for different clients
* **Development vs Production**: Separate environments for testing and live usage

### Developer Access Control

* **Developer-Accessible Workspaces**: Enable `developer_access = true` for workspaces that need OTP services and developer app integration
* **Standard Workspaces**: Keep `developer_access = false` for simple messaging campaigns

## Best Practices

### Workspace Organization

1. **Clear Naming**: Use descriptive names that indicate the workspace purpose
2. **Separate Environments**: Create different workspaces for development and production
3. **Enable Developer Access**: Only enable when you need OTP services or developer apps
4. **Documentation**: Keep track of what each workspace is used for

### Security Considerations

1. **Developer Access**: Only enable on workspaces that actually need OTP functionality
2. **Access Control**: Be mindful of which workspaces have developer access enabled
3. **Environment Separation**: Keep development and production workspaces separate