LM Providers

Language Model (LM) Providers are the outside AI services QAnswer talks to: the models that write answers, the ones that turn your documents into searchable vectors, and the tools that search the web, generate images or transcribe audio. This section explains what they are, where they are managed, and what each kind is for.

This page is the team's entry point: what each kind of provider is for, which of the organization's providers the team uses, and how the team default fits into the hierarchy.

The five kinds of provider

Each tab of the LM Providers page holds one kind of provider, and each kind has its own page in this documentation. You do not have to configure all of them — start with the ones your users actually need.

  • LLMthe models that read a question and write the answer. This is what users pick in the model selector of the chat.
  • Embedderthe models that turn documents into vectors so an assistant can search them. Every assistant is tied to one embedder.
  • Image Generationlets the chat and your assistants create images from a text prompt.
  • Speech-to-Textpowers the microphone button in the chat, so users can dictate instead of typing.
  • Web Searchlets a model look things up on the live web during a conversation.

Opening the page

In the team settings, click LM Providers in the left menu.

LM Providers in the team settings menu

The page opens on the LLM tab. The tabs across the top switch between the five kinds of provider; everything below the tabs works the same way on every tab.

What is specific to the team

A team has no catalogue of its own — it works from what the organization made available:

  • The list shows the providers the organization has activated. Switching one on or off here only changes what this team uses; the organization and the other teams are unaffected.
  • Set as default marks the team default, shown as a Team default badge. It applies to every member of the team who has not picked a personal default.
  • Add provider creates a provider from the team settings — use it when the team needs a model or an API key the organization has not made available.

Where you manage providers

The same LM Providers page exists at four levels. It looks and works the same everywhere — what changes is who your choices apply to.

  • Platformthe admin space of the installation. Providers created here form the catalogue of the whole platform: every organization can see and activate them. Reserved for platform administrators.
  • Organizationthe organization settings. Organization admins activate platform providers for their organization, add their own, and pick the organization defaults.
  • Teamthe same organization settings with a team selected in the workspace switcher. Team admins choose which of the organization's providers their team uses.
  • Your workspaceLM Providers in the main left menu. Everyone can pick their personal defaults there and plug in their own API keys.

This is the page as a team admin sees it — the providers the team can use, with the team default marked:

the LM Providers page of a team, with the team default marked on the first provider
Each level picks its own default

Each level picks its own default provider. When several levels have set one, the most specific level wins: personal over team, team over organization, organization over platform.

If you are setting this up for the first time

You normally do not need to change anything: the team inherits the organization's defaults, which is enough to chat and to build assistants. Come back here when the team needs a different model from the rest of the organization.

This page is just the entry point

How the list, the defaults, testing, adding and import/export work is described once for all levels in Managing LM Providers. What it all costs is in Usage and Costs.