Model Management

TextQL supports a range of AI models from Anthropic, OpenAI, and other providers. Organization administrators can control which models are available, set defaults, and decide whether users can switch models themselves. Model settings are found under Settings → Models, which has three tabs: Model Catalog, Role Access, and Analytics.

---

​

Available Models

TextQL’s model catalog includes models across several providers:

​

Anthropic (Claude)

* 1M token context window available in beta. Standard pricing applies up to 200K input tokens; tokens beyond 200K are billed at a higher rate. See Pricing for details.

​

OpenAI (GPT)

​

Google (Gemini)

​

Meta

​

DeepSeek (via Fireworks)

​

Moonshot (via Fireworks)

​

Zhipu / GLM (via Fireworks)

​

Qwen (via Fireworks)

For ACU pricing on each model, see the Pricing page.

---

​

Model Catalog

The Model Catalog tab is where administrators enable or disable models for the organization and set the organization-wide default.

​

Enabling and Disabling Models

By default, all models in the catalog are available to your organization. You can disable any model to prevent it from appearing in the model picker for all users. A disabled model cannot be selected by any user regardless of their role settings. If a role has a disabled model set as its default, the system default takes over.

​

Setting the Organization Default

The organization default is the model Ana uses when no specific model has been selected for a conversation. It appears as “Org Default” in role settings and is distinct from the System Default.

• System Default — TextQL’s platform-level default, currently Claude Sonnet 5 for Anthropic organizations and GPT-5.6 Sol for OpenAI organizations. This automatically updates as the platform evolves.
• Org Default — An explicit model your organization has pinned. Overrides the System Default for all roles that inherit from the org.

If no org default is set, all roles fall back to the System Default.

---

​

Role Access

The Role Access tab gives fine-grained control over which models each role can use, what their default is, and whether users in that role can switch models mid-conversation. Each role has three configurable settings:

​

Default Model

The model Ana starts a new conversation with for users in this role. Options are:

• Org Default — Inherits whatever the organization default is set to (recommended for most roles)
• System Default — Pins to TextQL’s platform default, auto-updating with the platform
• Specific model — Pins to an explicit model regardless of org or system defaults

​

Allowed Models

The subset of org-enabled models that users in this role can see in the model picker. Defaults to all enabled models. Restricting this is useful if you want certain roles to only access lower-cost or specific provider models.

Note: A role’s default model is always included in its allowed list. You cannot remove a model from the allowed list if it is set as that role’s default — change the role default first.

​

Can Switch

Controls whether users in this role see the model picker in the chat interface at all. When disabled, users in this role cannot change the model — they always use the role’s default.

​

Configuring via API

These three settings are fields on the role, set from this tab or programmatically with the role update API (RBACService/UpdateRole). They are not RBAC permissions and cannot be granted through a role’s permission list — allow_model_switching is a UI label, not a permission string. default_model_id and allowed_model_ids take LlmModel enum numbers. An empty allowed_model_ids is treated as “no change”; send clear_allowed_model_ids: true to reset it back to all models.

---

​

Model Picker (User-Facing)

When model switching is enabled for a role, users see a model picker in the top right of the chat interface. It shows:

• Default — The system/org/role default, auto-updating with the platform
• All models the role is allowed to access, grouped with provider icons

Hovering over a model for ~1 second expands its description. The currently selected model is highlighted with a checkmark. Models approaching deprecation show a warning icon with the deprecation date. A model selection is scoped to that conversation — switching models in one chat does not affect other chats.

---

​

Model Deprecations

When a model is scheduled for deprecation, a warning appears in the model picker next to that model’s name, showing the deprecation date. Administrators should update any role defaults that point to a deprecating model before the deprecation date to avoid disruption. After deprecation, requests to a deprecated model are automatically routed to the nearest equivalent current model.

---

​

Frequently Asked Questions

Can different roles use different providers (Anthropic vs OpenAI)? Yes. You can configure one role to default to Claude Sonnet and another to GPT-5.2 by setting explicit role defaults and restricting allowed models per role. What happens if a user’s role default model is disabled at the org level? The system falls back to the org default, then the system default. Disabled models are never served to users even if a role still references them. Does model selection affect Playbooks? Playbooks use the organization’s default model unless a specific model has been configured for that playbook. Role-level model restrictions do not apply to Playbook runs. Can I restrict users to only Anthropic models? Yes — set the allowed models for a role to only include Claude models. Users in that role will not see OpenAI or other provider options in the picker.