Opening the Settings and Initial Setup

This page shows how to reach the AnyLLM settings (administration page, admin UI, app configuration) in Jira and in Confluence, how the settings are organised, what the Home page tells you, in which order a first setup is safe, and what your later changes mean for the people using the chat.

What this does

The settings page AnyLLM Chat — Settings is the one place where AnyLLM is configured: LLM connections and API keys, endpoint approvals, site agents, templates and skills, usage statistics, import/export, module toggles and general settings. Because AnyLLM is one installation for Jira and Confluence, the page shows the same configuration in both products — only the endpoint approvals are confirmed per product (see Administration & Configuration).

Who can do this

Jira administrators and Confluence administrators. The settings page is protected by Atlassian: in Jira it requires Jira administration, in Confluence it requires Confluence administration. Endpoint approvals are additionally meant to be managed by Jira administrators — see Managing Endpoint Approvals.

Opening the settings

A shortcut exists inside the chat: administrators see a Settings button (gear icon, tooltip App settings (admins only)) — at the bottom of the sidebar on the app page, the fullscreen overlay and the standalone full page (as an icon when the sidebar is collapsed), and in the header of the Confluence macro and of the Jira issue navigator dialog. The compact surfaces (issue panel, issue sidebar panel, issue action, assistant dialog below the page title) do not show it.

How the chat decides whether to show the button:

• Jira: a real check of the administrator permission.
• Confluence: a group heuristic — the button appears if you are a member of one of the groups administrators, confluence-administrators, site-admins or confluence-admins. If your organisation grants Confluence administration through other groups, the button is missing; the route via Settings works regardless.

The button only controls visibility; the settings page itself is always protected by Atlassian.

Navigating the settings

The settings consist of nine sections, shown as tabs at the top of the page in this order:

• Switching to the other product: at the right of the tab row sits a button with an arrows icon and the name of the other product — Confluence when you are in Jira, Jira when you are in Confluence (tooltip: Open these settings in the other product (same configuration)). It opens the same configuration on the other product's settings page — the place where you grant that product's endpoint approvals.
• Keyboard: with a tab focused, Arrow Left and Arrow Right move between the sections, Home jumps to Home and End to General.
• Saving: the Save buttons on Connections (Save connections), Modules and General save the whole configuration at once — including connection cards you have edited but not yet saved and API keys typed there — and open Atlassian's approval dialog when a new endpoint is involved. Agents and Prompts & Skills have their own Save agents and Save prompts buttons.

The Home page

Home shows a short lead text and seven cards with live counts; clicking a card opens the corresponding section.

At the bottom the security model is summarised in one line: Security model: API keys never in the frontend · AI only with user permissions (asUser) · write actions only after confirmation in the chat · the app reaches no LLM endpoint you have not approved yourself.

Two notices can appear above the tabs on every settings page, not only on Home:

• a red alert, for example Configuration could not be loaded: … — the rest of the page is then not reliable; reload the page and, if the alert persists, see Troubleshooting;
• a yellow notice These endpoint domains are configured but not yet approved for this installation: … Until you approve them, requests to them are blocked — this typically happens after importing a configuration. with an Approve now button — see Managing Endpoint Approvals.

Installation order

AnyLLM is installed in Jira first; Confluence is then added to the same installation. A Confluence-only installation is not possible. Uninstalling the app from Jira removes it everywhere — together with the entire app storage of both products (configuration, conversations, memory, agents, templates, usage counters). See Licence, Data Retention and Automatic Deletion.

Safe order for initial setup

This order avoids states in which users see a half-configured app.

Changes during operation

• Rotating an API key: enter the new key in the API key field of the connection and click Save connections. The new key is used immediately, without downtime; leaving the field empty keeps the old key.
• Moving an endpoint: change the Endpoint of the connection, click Save connections and confirm Atlassian's dialog for the new address (or approve the new address beforehand under Endpoint approvals). After a successful save the app automatically revokes approvals that no saved connection or search service uses any more — the old address needs no manual revocation. Then grant the approval for the new address in the other product as well (Approve now in the Approval status per product table).
• Tightening AI access (for example Read + write → Read only): takes effect immediately. Suggestion cards that are still open can no longer be executed; clicking ✓ Execute then fails with "Write actions are not enabled by the admin."
• Removing a connection or deleting its key: its models disappear from every user's selection immediately; details in Setting Up LLM Connections.

Effects of admin changes on users

Related topics

• Administration & Configuration
• Setting Up LLM Connections
• Managing Endpoint Approvals
• General Settings
• Modules: Switching Surfaces On and Off
• Permissions, Roles and Data Visibility
• Getting Started
• Troubleshooting
• FAQ