# Namespace and Collection

ChatBees organizes data into Namespaces and Collections. A Collection serves as the fundamental unit for data organization. You can put different data sets into different collections. Meanwhile, a Namespace acts as a higher-level organizational construct for Collections. Within a Namespace, multiple Collections can be created to further categorize data.

You can think about namespace like a schema and collection like a table in Database. Once we fully support user management and Role-Based Access Control (RBAC) features, Namespaces can facilitate efficient permission management. For instance, all Collections belonging to a specific Business Unit (BU) could be grouped under a single Namespace, simplifying access permission assignment by granting access to a role at the Namespace level. This way you don't need to repeat the access permission management for every collection.

{% hint style="info" %}
Currently, the creation of new namespaces is not supported. Each account automatically comes with a default namespace, named "public". When accessing ChatBees REST APIs, please ensure that the namespace is set to "public".
{% endhint %}


---

# 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.chatbees.ai/chatbees/concepts/namespace-and-collection.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.