# Overview

### **Why Organizations & Workspaces Exist**

Qolaba is designed to work seamlessly for both individuals and teams. As your usage grows—across projects, clients, or departments—you need a structured way to manage credits, organize work, and collaborate efficiently.

**Organizations and Workspaces provide that structure.**

They help you move from isolated usage to a more **organized, collaborative, and scalable setup**, without losing visibility or control.

***

### Key Challenges Addressed

<table><thead><tr><th width="188.02032470703125">Challenge</th><th>Without Structure</th><th>With Organizations &#x26; Workspaces</th></tr></thead><tbody><tr><td>Credit management</td><td>Scattered usage across users</td><td>Centralized credit pool or Separate Workspace Budgets</td></tr><tr><td>Collaboration</td><td>Disconnected workflows</td><td>Shared environment</td></tr><tr><td>Access control</td><td>No clear permissions</td><td>Role-based access</td></tr><tr><td>Organization</td><td>Mixed outputs and history</td><td>Structured workspaces</td></tr><tr><td>Visibility</td><td>Difficult to track usage</td><td>Clear usage tracking</td></tr></tbody></table>

***

### Core Capabilities

#### **1. Centralized Credit Management**

All usage in Qolaba is credit-based. Instead of managing credits individually, organizations introduce a **shared system**:

* A single subscription and billing source
* Allocate budgets to each workspace or consume from shared pool
* Centralized top-ups and plan management
* Visibility into overall usage

This makes it easier to control costs and avoid fragmented credit usage across multiple users.

***

#### **2. Structured Collaboration**

Organizations and Workspaces allow teams to collaborate in a structured and organized way, while keeping work relevant to each role.

* Different teams or functions can work within their own **dedicated workspaces**
* Each workspace can focus on specific tasks or workflows
* Usage and outputs remain organized and easy to track

{% hint style="info" %}
**Example: Team Workflow**

A team organizes work across multiple workspaces:

* In the **Research workspace**:\
  Members use **Chat (LLMs)** to generate insights, content ideas, and strategy inputs
* In the **Design workspace**:\
  Members use **Image and Video tools** to create visuals and assets
* In the **Content workspace**:\
  Members refine messaging, scripts, and final outputs

Each team works within its own context, while all activity stays connected under the same organization.
{% endhint %}

***

#### **3. Clear Separation of Work**

As more work is created, keeping everything in one place becomes difficult to manage.

Workspaces help you structure work based on your needs, such as:

* Projects or clients
* Teams or departments
* Use cases or workflows

Each workspace acts as an independent environment, helping you keep work cleanly separated without affecting other teams.

***

#### **4. Usage Visibility**

Organizations provide a clear view of how credits are being used across your team.

You can:

* Monitor usage across different workspaces
* Track activity at a member level
* Analyze usage across tools (Chat, Image, Video, Audio)

This level of visibility helps teams stay **in control of usage and spending**.

***

### Summary

Organizations and Workspaces form the foundation for using Qolaba effectively at scale.

They allow you to:

* Manage credits from a single place
* Collaborate without overlap
* Keep work structured and easy to navigate
* Maintain visibility into usage

Whether you're working solo or as part of a team, this structure ensures your workflows remain **organized, flexible, and scalable**.

***

### Suggested Next Steps

To learn more, explore:

* [Creating an Organization](/organization-and-workspaces/organizations/creating-an-organization.md)
* [Creating and Managing Workspaces](/organization-and-workspaces/workspaces.md)
* [Inviting and Managing Members](/getting-started/introduction.md)
* [Credits and Usage Tracking](/organization-and-workspaces/tracking-credits-and-ai-usage.md)


---

# 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/overview.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.