Multi-tenant implementation guide
The following architecture is recommended for multi-tenant requirements in customer service scenarios:
- tenant segregation: Assign separate API keys and namespaces for each client
- Resource allocation: Configured through the Tenant Management interface of the console:
- Exclusive model quota
- Private plugin permissions
- Separate data sets - unified interface: Utilize Project functionality to maintain common workflow templates for different tenants
- Customized extensions: Develop customized tools for specific customers (subject to plug-in development specifications)
Typical Configuration Example: Financial services customers can exclusively configure the Stock Data Plug-in + Sensitive Information Filtering module.
This answer comes from the articleTaskingAI: An Open Source Platform for Developing AI Native ApplicationsThe































