Setting Up LLM Connections

This page explains how to set up the LLM connections (AI services, endpoints, API keys, model lists) that AnyLLM uses: creating a connection, confirming Atlassian's approval dialog, testing the connection, changing or deleting an API key and removing a connection.

What this does

A connection is an AI service that you make available: an address (endpoint), a provider type, the names of the models your users may choose from and an API key. Up to 5 connections with up to 20 models each are possible per installation — a saved connection is available to the users of Jira and of Confluence alike. Only connections with a stored API key are offered to users; their models appear in the model selection of the chat, grouped under the connection name.

Who can do this

Product administrators (Jira or Confluence administration). The Connections page is the same in both products.

Before you start

• You have the address of the service, the API key and the exact model names at hand. For OpenAI-compatible services the address includes /v1, for example https://llm.my-company.com/v1. Only https addresses are accepted.
• Saving a connection with a new address opens Atlassian's approval dialog — its consent counts only for the product you are working in. Plan to open the settings in the other product afterwards and approve the address there as well (see Managing Endpoint Approvals).
• Open Settings → Connections (route: Opening the Settings and Initial Setup).

Creating a connection

Purpose — make an AI service available to all users of the installation.

Steps

1. Click + Add connection. A new card appears (titled Connection {n} until you enter a name).
2. Fill in the fields of the card:

1. Click Save connections.
2. Confirm Atlassian's confirmation dialog AnyLLM: self-hosted LLM endpoints (…) — it lists all addresses of the app's approval group, also when you add only one.
3. Switch to the other product with the product button at the top of the settings and grant the approval there too: Approve now in the Approval status per product table on the Endpoint approvals page.

Provider types

Expected result — the message Saved. next to the button. The label of the API key field now reads API key (set — leave empty to keep, a new value rotates it), and the address appears as approved for this product under Endpoint approvals. Users see the models of the connection in their model selection; requests succeed once the approval exists in their product.

Notes

• If the dialog is declined, nothing is saved: the page reports Network approval for … was declined or failed — nothing was saved. (a technical failure of the dialog looks the same). Save again and confirm.
• The approval counts only for this product. Until you approve the address in the other product as well, the chat there answers The endpoint {host} is not approved for {p} yet — endpoint approvals apply per product. …
• Five connections are the maximum: once five cards exist, + Add connection disappears (an import keeps only the first five cards). Remove a connection to make room.
• Save on other pages also saves your cards: the Save buttons on Modules and General submit the whole configuration, including edited connection cards and keys typed there.
• Automatic clean-up: after a successful save, the app revokes approvals that no saved connection or search service uses any more.
• If the page reports Saved, but the network approval could not be requested — customer-managed egress is not available for this installation. … in red, the configuration was saved, but Atlassian's approval function is missing — see Managing Endpoint Approvals.

Testing a connection

Prerequisite — the connection is saved and has a key. Until the card is saved it says New — test available after saving.; Test connection stays disabled as long as the connection is unsaved or has no key.

Steps

1. Click Test connection on the card. While the test runs, the card shows Testing connection ….
2. Read the response:

Expected result — a successful test in a product also clears a "blocked" entry of that product on the Endpoint approvals page. The test works regardless of the subscription state.

Changing or deleting an API key

Changing: enter the new key in the API key field — the field is empty and its label carries (set — leave empty to keep, a new value rotates it) — and click Save connections. The new key is used immediately; an empty field keeps the old key.

Deleting:

1. Click Delete key on the card. The button changes to Really delete?.
2. Click Really delete? to confirm. No further save is needed.

Expected result — the card reports API key deleted — connection is disabled until a new key is saved. On failure it shows Delete failed. or Connection not found.

⚠️ Warning: Without a key the connection is disabled immediately. Its models disappear from every user's selection. If one of them was the default model, users automatically get the first available model of another connection. If no usable connection is left, the chat reports Not configured yet … and the input field is locked.

Removing a connection

1. Click Remove on the connection card (shown only while more than one card exists).
2. Click Save connections.

Expected result — Saved. The connection and its stored key are gone; users lose that connection's models. Conversations already saved are kept; when continued, an available model is used instead. An approval that no other saved connection or search service uses is revoked automatically after the save.

Common problems

Server messages appear in English next to the Save connections button.

Related topics

• Administration & Configuration
• Opening the Settings and Initial Setup
• Managing Endpoint Approvals
• General Settings
• Enabling Web Search and Image Generation
• Usage Statistics, Import/Export and Backup
• Chatting with the AI
• Troubleshooting
• FAQ