Skip to content

Tenant Settings Flows

Load-edit-save cycle

sequenceDiagram
    participant UI as Settings UI
    participant API as Core Config API
    participant DB as Config storage
    UI->>API: GET /api/core/config/:id
    API->>DB: Assemble nested config from cConfigExt
    API-->>UI: Return full snapshot
    UI->>API: PUT or PATCH with changed data
    API->>DB: Preserve secrets if needed and save changed sections
    API-->>UI: Return refreshed snapshot

Realtime refresh behavior

sequenceDiagram
    participant RT as Realtime topic
    participant UI as Settings UI
    RT-->>UI: config.changed
    UI->>UI: If editing, postpone refresh
    UI->>API: Refetch after edit mode ends

This reduces accidental form disruption while still keeping the screen eventually consistent with background changes.

Connection verification flow

Settings can trigger CPI or Edge connection checks after a tenant already exists. That is operationally important when credentials, URLs, proxies, or certificates have changed.

Side-effect flow

A settings save can update more than the raw config blob:

  • access-group assignments may be synchronized
  • AI scenario settings may be updated
  • runtime jobs will consume the new config on their next cycle