Skip to content

Tenant Settings Modules

Primary frontend module

  • frontend/src/pages/components/config/ConfigSettings.jsx Main editor for general data, connection details, query behavior, AI scenarios, and job tuning.

Support modules

  • frontend/src/pages/components/config/configSave.js Shared save logic reused by settings-related editing surfaces.
  • frontend/src/pages/components/config/settings/configSettingsHelpContent.js Contextual help registry.
  • frontend/src/pages/components/config/settings/ConfigSettingsHelpPopover.jsx Inline help trigger.
  • frontend/src/pages/components/config/settings/ConfigSettingsDocumentationModal.jsx Extended docs entry for the settings area.

Backend counterparts

  • backend/src/core/views.py Loads assembled config data and persists changes back into cConfig and cConfigExt.
  • backend/src/cpi/views.py Supplies supporting runtime views that depend on the settings outcome later, such as alerts, messages, packages, archives, and keystore data.

Data relationships

  • cConfig Root tenant metadata and enable or disable state.
  • cConfigExt Split config and runtime sections, including connection, global, jobs.*, and periodic.
  • related group and role assignment tables Used for tenant visibility and scoped access.

Runtime-specific UI behavior

The settings screen is more than a form:

  • it reacts to backend updates through realtime topics
  • it pauses refresh while the user is editing
  • it sanitizes secrets before re-rendering loaded state
  • it synchronizes related access-group assignments beside the main config save