Modules: Switching Surfaces On and Off

This page shows how to switch the individual AnyLLM surfaces (modules, entry points, chat panels and quick actions) on and off for the whole site on the settings page Modules, and what users notice when a surface is disabled.

What this does

Every place where AnyLLM appears in Jira or Confluence — the app page, panels, dialogs, quick actions, the chat bar, the gadget, the standalone full page — is a module with its own toggle. Modules lists 14 toggles in three groups (Confluence, Jira, Across products); all are switched on by default. The Home page shows how many are enabled (e.g. "14 of 14 surfaces enabled").

Disabling a module works in two layers: the surface shows a notice instead of the chat, and the server additionally rejects every request from that module (fail-closed) — so nothing can slip through a stale browser tab.

Who can do this

Product administrators (Jira or Confluence administration) on the settings page AnyLLM Chat — Settings — see Opening the Settings and Initial Setup.

Before you start

For a first setup, a safe order is to leave only the surfaces enabled that you want to start with and enable the rest once connections and approvals work — see Opening the Settings and Initial Setup.

Step by step

1. Open Settings → Modules.
2. Tick or untick the toggles. Each toggle is labelled label — description exactly as in the tables below.
3. Click Save.

Expected result — the status reads Saved. The change applies site-wide and immediately (exception: the chat bar, see below). Requests from a disabled module are rejected from now on.

The toggles

Confluence

Jira

Across products

What users notice when a module is off

• Menu entries do not disappear. Atlassian does not allow an app to hide its menu entries per installation. The entry stays visible; whoever opens it sees only "This feature has been disabled by your administrator." — on the assistant dialog below the page title, the issue action and the issue navigator with a Close link underneath. A disabled dashboard gadget shows the notice in view and edit mode. Disabled Confluence quick actions show the notice with a Close button.
• The chat bar hides itself completely — no notice. Its status is cached in each person's browser for 10 minutes in both directions: after you switch it off, it may stay visible for up to 10 minutes on pages already visited; after you switch it back on (or finish the setup), a bar cached as hidden may stay hidden for up to 10 minutes as well.
• The fullscreen overlay follows its opener. In Jira, Fullscreen chat (Jira) governs the ⤢ Fullscreen overlay opened from issue surfaces (issue panel, issue sidebar panel, issue action, issue navigator); with the toggle off, the overlay shows the disabled notice even if the surface it was opened from is on. In Confluence, the overlay opened by the chat bar belongs to Chat bar (page banner).
• The command palette in Jira has no toggle of its own. Its entry AnyLLM Chat only navigates to the app page and therefore follows Global page (Jira).
• The link to the standalone full page stays visible at the bottom of the sidebar even when Standalone full page is off; the page itself then shows the disabled notice.
• The toggles apply to the whole site — Jira and Confluence share one configuration; there is nothing to repeat in the other product.
• The settings page itself is never affected by the toggles.

Common problems

Related topics

• Administration & Configuration
• Opening the Settings and Initial Setup
• General Settings: Language, Default Model, AI Access, Rate Limit, Site Knowledge
• AnyLLM in Confluence — Chat Bar, Quick Actions, Page Assistant and Macro
• AnyLLM in Jira — Issue Panel, Sidebar Panel, Issue Navigator and Command Palette
• Dashboard Gadget (AI Report)
• Getting Started — where AnyLLM appears
• Permissions, Roles and Data Visibility
• Troubleshooting
• FAQ