Is your feature request related to a problem? Please describe.
Currently, channels in AzulClaw are not able to support multi-user scenarios. For instance, integrating Telegram as a channel restricts usage to a single Telegram account per AzulClaw instance, leading to a one-to-one mapping between a communication channel and an internal user or agent. AzulClaw, positioned as a business-ready AI assistant solution, must accommodate enterprise requirements where multiple employees or groups operate under the same Azure infrastructure. Enterprises often require multiple, parallel installations of AzulClaw with isolated but shared access to communication channels—something the current architecture does not facilitate.
This limitation presents a significant barrier for enterprise adoption, as there is no mechanism to individually route incoming messages from external users (e.g., distinct Telegram IDs) to the appropriate AzulClaw instance or employee within the same business environment. This results in inefficiencies, potential privacy issues, and prevents centralized, scalable support for multiple employees or departments sharing communication infrastructure.
Describe the solution you'd like
The proposed enhancement is to implement true multi-user support for channel integrations (with an initial focus on Telegram):
- Design and implement a mapping system that associates external user identifiers (e.g., Telegram user IDs) with specific AzulClaw instances or employee endpoints.
- Update the message handling and queuing mechanism to automatically determine and delegate each incoming message to the relevant AzulClaw instance or user, based on this mapping.
- Ensure that the architecture can support several parallel user sessions under the same channel integration without message collision or routing errors.
- Integrate a secure administrative interface for managing user-to-instance mappings, enabling dynamic assignment or reassignment of external users to internal endpoints, as required by business context.
- Maintain robust separation and privacy of communications between different company users, even when operating under a unified infrastructure and shared channels.
Describe alternatives you've considered
- Deploying and maintaining separate bot/channel instances for every employee, which introduces overhead, increased management complexity, and cost.
- Using shared groups or broadcast channels, which does not guarantee message privacy or efficient targeted communication.
Additional context
This enhancement is crucial to align AzulClaw with enterprise best practices, ensuring the solution can securely and efficiently scale to support diverse organizational structures and multi-user workflows. Providing this flexibility will enhance usability, reduce operational friction, and strengthen AzulClaw’s value proposition for business-critical applications.
Is your feature request related to a problem? Please describe.
Currently, channels in AzulClaw are not able to support multi-user scenarios. For instance, integrating Telegram as a channel restricts usage to a single Telegram account per AzulClaw instance, leading to a one-to-one mapping between a communication channel and an internal user or agent. AzulClaw, positioned as a business-ready AI assistant solution, must accommodate enterprise requirements where multiple employees or groups operate under the same Azure infrastructure. Enterprises often require multiple, parallel installations of AzulClaw with isolated but shared access to communication channels—something the current architecture does not facilitate.
This limitation presents a significant barrier for enterprise adoption, as there is no mechanism to individually route incoming messages from external users (e.g., distinct Telegram IDs) to the appropriate AzulClaw instance or employee within the same business environment. This results in inefficiencies, potential privacy issues, and prevents centralized, scalable support for multiple employees or departments sharing communication infrastructure.
Describe the solution you'd like
The proposed enhancement is to implement true multi-user support for channel integrations (with an initial focus on Telegram):
Describe alternatives you've considered
Additional context
This enhancement is crucial to align AzulClaw with enterprise best practices, ensuring the solution can securely and efficiently scale to support diverse organizational structures and multi-user workflows. Providing this flexibility will enhance usability, reduce operational friction, and strengthen AzulClaw’s value proposition for business-critical applications.