Skip to main content Skip to page footer

Overview of settings in the backend module

Since versions 14.0.0/13.12.0/12.18.0, the central AI Suite settings can be maintained directly in the backend. Access is via the entry “Global Settings” (gear icon) in the backend module “AI Suite” (in a narrow view via the “More” menu) or via the “Settings” dashboard card. This is the convenient alternative to the file-based configuration in the Install Tool and writes to the same values. The button only appears if the permission “Enable ‘Global Settings’ section within backend module” (enable_global_settings) is set, see permission management.

  • Open the settings: The “AI Suite” module

    In the backend module “AI Suite”, we open the menu item “Global Settings” (in a narrow view via the “More” menu).

Note on Sensitive Fields

API keys and the Basic Auth password are displayed masked. If you leave the placeholder (************) unchanged, the saved value is kept. If you enter a new value, it is applied when saving. If you clear the field instead, the saved key is deleted.

Managed Settings Areas

Since versions 14.6.2/13.18.2/12.24.2, the areas correspond to the tabs of the extension configuration. Since versions 14.7.0/13.19.0/12.25.0, every section of an area sits in its own frame with its heading:

  • License & server: License key (aiSuiteApiKey), server URL (aiSuiteServer), system domain (aiSuiteSystemDomain), data protection with the option “Only load GDPR-compliant libraries” (forceGdpa, see below), HTTP basic auth (enable, user, password)
  • Audits: WCAG standard (auditWcagStandard), default text model for audits (auditDefaultTextModel)
  • Translation: Disable translation function, translate FlexForm fields, translate “Plain HTML” content elements (translatePlainHtml, since versions 14.7.0/13.19.0/12.25.0), library for “Easy Language”, automatic translation on save (incl. mode, model and maximum number of elements per save operation)
  • Metadata: Number of suggestions, minimum length of the page content (minPlausiblePageContentLength), automatic generation of title/alternative text on file upload (the section points out that it only applies to newly uploaded files and leaves existing files unchanged), model, procedure (TaskEngine or save directly), own prompt for the automatic generation (metadataAutogeneratePrompt, since versions 14.4.0/13.16.0/12.22.0)
  • Media: Storage folder for generated media (mediaStorageFolder)
  • CLI: Maximum number of CLI background tasks per scheduler run (maxTasks). The limit also applies to ai-suite:retry-tasks.
  • EU AI Act: Recording of AI-written content, disclosure of translations, marking in the backend (provenanceTracking, provenanceDiscloseTranslations, provenanceShowLabels), see AI Content (EU AI Act)
  • Own API keys: OpenAI, Anthropic, AI Model Hub (IONOS, also used for Flux), Mittwald AI Model Hub (for the Mittwald models), Staan (only for web research in GDPR mode with your own keys), Google Translate, DeepL (incl. free API mode), Midjourney (key + ID)
  • The sections: Audits

    Below follow the sections “Audits”, “Translation”, “Metadata”, “Media”, “CLI”, “EU AI Act” and “Own API keys”. Each one can be expanded.

  • Save: Save settings

    With “Save Settings” we apply the changes.

    GDPR Mode

    The option “Only load GDPR-compliant libraries” (forceGdpa, default: off) in the “License & server” area restricts the available AI models to those marked as GDPR-compliant on the AI Suite server. Enable the option if only data protection-compliant models are to be used.

    • License and server: License and server

      At the very top, “License & server” holds the license key and the server address, made unreadable here. There we can also set that only GDPR-compliant libraries are loaded.