ChatBees
  • 👋Welcome
  • Concepts
    • 📖Architecture
    • 📖Security
    • 📖Serverless RAG
    • 📖Namespace and Collection
    • 📖Access Control
    • 🚀Ticket AI Agent
  • Ticket AI Agent
    • Installation
  • WEB APP REFERENCES
    • 🔑Sign-in and Sign-out
    • ⛓️Manage Connectors
    • 🌏Manage Collections
      • 💿Data Sources
        • 📖Configure Periodic Import
      • ❓Chat with collection
      • ⏱️View Q/A history
      • 📖Publish a Collection
    • 🏛️Manage Users
    • 💰[Flex] Billing and Payment
    • 💰[Enterprise] Billing and Payment
    • 📈Account Usage
    • 🗝️API Keys
    • 🖥️Generated Code Sample
  • ChatBots
    • 🪄AI Chat for Confluence
    • 🪄ChatBees Slack Bot
    • 🪄ChatBees Website ChatBot
    • 🪄Pnyx Discord Bot
  • Snowflake Native App
  • API References
    • 📖API Key
    • 📖Collection Operations
      • 📖Create Collection
      • 📖Configure Collection
      • 📖List Collections
      • 📖Delete Collection
    • 📖Document Operations
      • 📖Upload Document
      • 📖Summarize Document
      • 📖Get Document Outlines and FAQs
      • 📖Ask
      • 📖Chat
      • 📖Search
      • 📖Personalize Response
      • 📖List Documents
      • 📖Delete Document
    • 📖Crawl Operations
      • 📖Create Crawl
      • 📖Get Crawl
      • 📖Index Crawl
      • 📖Delete Crawl
    • 📖Ingest Data Sources
      • 📖Create Ingestion
      • 📖Get Ingestion
      • 📖Index Ingestion
      • 📖Delete Ingestion
Powered by GitBook
On this page
  1. Concepts

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.

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".

PreviousServerless RAGNextAccess Control

Last updated 1 year ago

📖