Skip to main content

Overview

Model configurations define which AI language models are available in your Experio deployment. You can configure multiple models from different providers and control which ones are available to end users. Navigate to Admin > Settings > Model Configurations.

Viewing Models

The model configurations page lists all configured models with:
  • Name (internal identifier)
  • Display Name (shown to users)
  • Type (see Model Types)
  • Provider
  • Active status
  • User-Facing status (whether end users can select this model)

Creating a Model Configuration

Click Create New and fill in:

Model Types

Assign ingestion models in System Settings:
  • CLASSIFICATION_MODEL_CONFIG
  • INGESTION_LARGE_MODEL_CONFIG
  • INGESTION_MEDIUM_MODEL_CONFIG (optional; used when a content type sets model_tier: medium)
  • INGESTION_SMALL_MODEL_CONFIG
  • DECISION_MODEL_CONFIG (optional; enables graph evaluation triage)
Content types can override the primary tier per type. See Extraction Policy.

Decision models

A Decision model uses the Foundry Decision provider (Microsoft-Decision-1 on Microsoft Foundry). It doesn’t generate text, so it can’t be used for chat or ingestion, and the Foundry Decision provider can’t be used for any other type. Its API configuration is:
deployment is your deployment name, not the model name. endpoint can also be the full .../providers/microsoft/v1/systemone URL from the Foundry portal. timeout_seconds is optional. Test Connection asks the model one yes/no question and shows the probability it returned.

Testing Connections

Before activating a model, test its connection:
  1. Click Test Connection on any model
  2. The system sends a real API request to the provider
  3. Results show:
    • Response time
    • Response preview
    • Embedding dimensions (for embedding models)
    • Success or error status
Always test a model connection after creation or after changing API configuration. This validates credentials, endpoints, and model availability before end users encounter issues.

Managing Models

Editing

Click any model to edit its configuration. Changes to API configuration or active status take effect immediately.

Activating/Deactivating

Toggle the Active status to enable or disable a model. Deactivated models are not available for any operation. Toggle the User-Facing status to control whether end users see the model in the model selector dropdown. Non-user-facing models can still be used by assistants as their default model.

Deleting

Remove a model configuration permanently. Ensure no assistants are configured to use the model before deleting.