# Workspaces

Workspaces are structured environments inside an organization that allow teams to separate projects, clients, or departments while sharing the same subscription. They act as controlled containers for AI usage. Workspaces can access credits directly from the shared pool or through their allocated budgets.

### What is a Workspace?

A workspace is a **project-level container** within an organization designed to structure and manage AI operations.

It is used to:

* Organize AI work by project, team, or client
* Maintain separation between different use cases
* Track credit usage independently
* Preserve clean and isolated activity history

#### Common Use Cases

| User Type       | Workspace per... | Example                       | Benefit                       |
| --------------- | ---------------- | ----------------------------- | ----------------------------- |
| Agency          | Client           | Workspace: Nike Campaign      | Data isolation, clean billing |
| SMB             | Department       | Workspace: Marketing          | Usage tracking per team       |
| Consultant      | Engagement       | Workspace: Q3 Audit           | Client confidentiality        |
| Freelancer      | Revenue stream   | Workspace: Brand A            | Isolated outputs              |
| Dev / R\&D Team | Experiment       | Workspace: GPT vs Claude Test | No production interference    |

***

### Key Capabilities

#### 1. Project or Client-Level Structuring

A workspace can represent different operational units such as:

* Clients
* Departments
* Campaigns
* Product lines
* Research initiatives
* Consulting engagements

This prevents overlap between unrelated work and ensures structured execution.

#### 2. Independent Usage Tracking

Although credits belong to the organization, usage is tracked at the workspace level.

Each workspace provides visibility into:

* Image and speech credit consumption
* Chatbot credit usage
* Total credits consumed

This enables accurate:

* Client billing
* Department budgeting
* Resource forecasting
* Performance analysis

#### 3. Isolated AI History

Every workspace maintains its own activity history.

This ensures:

* No cross-workspace visibility of generated content
* Project-specific conversations remain contained
* Outputs and media are properly organized

This isolation supports confidentiality, privacy, and clean workflows.

***

### Primary Workspace

When an organization is created, **Qolaba automatically generates the first workspace**, known as the **Primary Workspace**.

The Primary Workspace:

* Is the first workspace created by default
* Serves as the initial working environment

This ensures the organization is immediately ready for use without additional setup.

***

#### Default Workspace Behavior

The Primary Workspace acts as the default workspace for all initial activities.

This means:

* All initial AI activity is recorded here
* History is stored by default in this workspace
* Members operate within it unless reassigned

If no additional workspaces are created, all activity remains within the Primary Workspace.

#### When Should You Create Additional Workspaces?

You should create new workspaces when:

* Managing multiple clients
* Operating across different departments
* Requiring separate credit tracking per project
* Needing isolated AI history
* Enforcing stricter project-level governance

Workspaces are essential for maintaining scalability, clarity, and operational control.

***

### Organization vs Workspace

<table><thead><tr><th width="136.84375">Aspect</th><th>Organization</th><th>Workspace</th></tr></thead><tbody><tr><td>Role</td><td>Top-level entity</td><td>Project-level container</td></tr><tr><td>Ownership</td><td>Owns subscription and credits</td><td>Uses allocated or shared credits</td></tr><tr><td>Management</td><td>Manages members</td><td>Assigns members per project</td></tr><tr><td>Function</td><td>Contains workspaces</td><td>Segments and organizes work</td></tr><tr><td>Data Scope</td><td>Global</td><td>Isolated per workspace</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.qolaba.ai/organization-and-workspaces/workspaces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.