Model Management

Create a New Model Set

Administrators can create a new model set by following these steps:

1. Navigate to the Model Set Management Page: Go to Model Management, then click on "Model Set".

2. Click "New": Click the "New" button on the right side of the page to start creating a new model set.

3. Select Model Type: In the pop-up window, choose the type of model. Available types include:

   • LLM (Large Language Model)

   • Embedding (Embedding Model)

💡 Tip: The system only supports adding one Embedding.

4. Select Language Model: Choose the appropriate language model based on your needs. Currently supported language models include:

• LLM language models: OpenAI, Deepseek, Azure, Ollama, Tongyi, Qianfan;

• Embedding language models: OpenA Embeddings, Azure Embeddings, AliEmbeddings, Ollama Embeddings;

5. Fill in Model Set Information: Enter the name and description of the model set, ensuring the information is clear and accurate (name within 50 characters, description within 200 characters).

6. Select Additional Settings: Choose whether to support image Q&A and whether it is an inference model according to your needs.

7. Save Creation: After completing the form, click the "Save" button to complete the creation of the model set.

By following these steps, administrators can successfully create a new model set and configure the corresponding settings.

Default Model

In model management, administrators can set default models to specify applicable models for different usage scenarios. For example, in BI (Business Intelligence), and other scenarios, the default model can be set to the gpt-4.1 model. This way, the system will automatically use the preset default model in the corresponding scenarios, improving work efficiency and consistency.

The setup steps are similar to creating a model set, and administrators can select the appropriate model as the default model for the scenario based on actual needs.

Usage Scenarios

Create Model Group

Administrators can create model groups in model management. The created model groups can be configured for assistants during their creation.

The steps to create a model group are as follows:

1. Navigate to the Model Group Management Page: Go to Management, select "Model Management", then click "Model Group".

2. Click "New Model Group": Click the "New Model Group" button on the right side of the page to start creating a new model group.

3. Enter Model Group Name: Assign a unique name to the model group for easy identification (within 50 characters).

4. Select Models: Choose the models to include in the model group from the available model list; multiple selections are supported.

5. Choose Whether to Enable Adaptive Model Deployment: Select whether to enable adaptive model deployment to improve model flexibility and adaptability according to needs.

6. Choose Whether to Enable Deep Thinking Model: Select whether to enable the deep thinking model to enhance the model's intelligent processing capability as needed.

7. Click "Save": After confirming all settings are correct, click the "Save" button to successfully create the model group.

Model Group Channel Details

After creating a new model group, you can enter the "Channel Details" page to view all configured channels. You can:

• Create new channels;

• Or click the right-side "Key Details" to view all key information under that channel and support creating new keys.

This page facilitates unified management of channels and their corresponding API Keys.

The API Keys provided by our platform have a high degree of independence and authorization effectiveness. Each API Key is equivalent to an independent "passport", possessing full access and invocation permissions, detailed as follows:

• Independent of the platform user system
  Callers holding an API Key do not need to be registered users of the platform nor have any specific user permissions. As long as the request carries a valid API Key, it will be regarded as a legally authorized request, and the system will process and respond normally.

• Not restricted by License
  Calls initiated via API Key do not consume the platform's user License quota. Therefore, even if the actual number of registered users on the platform is limited, more service access and business scenarios can be flexibly supported through API Keys, achieving scalable use without additional authorization or expansion.

• Flexible configuration as needed
  Different API Keys can be configured with different validity periods and permission scopes (such as access modules, data ranges, etc.) to adapt to different integration systems or business parties. It is recommended to generate a separate API Key for each integration party for easier subsequent management and usage tracking.

⚠️ Security Reminder: Please manage API Keys properly to avoid leakage. Once abused externally, all requests initiated through that Key will have full permissions by default, which may pose risks to data and system security.

Model Configuration Instructions

This product supports integration of the following enhanced features, all relying on services provided by Azure or external platforms. You need to select and obtain the necessary access credentials (API Key, Endpoint, etc.) from the relevant platforms according to your own needs:

1. Voice Input Function (Whisper Service)

   • Service Description: Purchase and deploy the Whisper service on Azure to achieve speech-to-text functionality.

   • Configuration Method: Supports configuring multiple Whisper Keys via environment variables, with variable names clearly containing the word "Whisper"; if not configured, the voice input button will not be displayed.

   • Compatibility Note: Also supports configuring Whisper service via SQL initialization; the configuration content will be automatically written into environment variables and supports later modification.

2. Azure OCR Mode (Azure Document Intelligence)

   • Service Description: OCR capability based on Azure Document Intelligence, supporting two recognition modes: "Basic" and "Advanced".

   • Configuration Method: Requires setting the Azure OCR mode KEY and Endpoint in environment variables; if not configured, this OCR mode cannot be selected.

   • Interaction Prompt: The interface will automatically display selectable modes based on configuration status and restrict selection of invalid options.