Skip to main content

Configuration

Overview​

The Configuration page allows administrators to manage global settings that affect the entire application. These settings include options for AI data sources, semantic search configurations, database migration, dashboard settings, and assistance features.

  • Select the Configuration tab to load the Global Configuration page.
    Global Configuration

Sections​

Global Configuration​

Overview​

Global Configuration refers to the application-wide settings that affect all users, modules, under tenant. These settings are typically managed by administrators and are used to define default behaviors, integrations, and platform-level features.

Global configurations ensure consistency across the application and streamline the management of core functionalities.

Key Characteristics​

  • Applies system-wide across all users and modules.
  • Typically managed by admin-level users.
  • Changes made at the global level are automatically reflected wherever relevant across the application.
  • Often includes integration settings, feature toggles, data source selections, and default policies.

Configuration Options​

The Global Configuration section includes the following options:

  1. AI Data Source
    • The AI Data Source section lists all available LLM (Large Language Model) data sources (OpenAI Model or Ollama Model types).
    • Users can select any data source from the list and click the SUBMIT button.
    • The selected LLM data source will be used for multiple AI features, including:
      • AI Studio
      • Universal Semantic Search
    • The LLM data source can be updated at any time.
Tenant-Wide Availability

The selected AI Data Source is automatically available to all users within the tenant. Normal users do not need to create their own AI data source — they can use the one configured globally by the tenant administrator.

:::

Best Practices​

  • Document any changes made and their impact.
  • Review and audit settings regularly.
  • Communicate changes to affected teams before rollout.

Universal Semantic Search Configuration​

Overview​

Universal Semantic Search is an advanced search feature that goes beyond traditional keyword matching. It understands the context, intent, and meaning of user queries, delivering more accurate and relevant results across various modules within the application.

This feature can be configured at the tenant level and tailored to specific modules and users.

  • Navigate to Universal Semantic Search via the Settings → Configuration page.

Configuration Options​

This section includes the following configurable options:

1. Search Type​

Three search types are available:

  • Full Text Search – Traditional keyword-based search.
  • Semantic Search – Meaning-based search.
  • Hybrid Search – Combines both Full Text and Semantic Search.

uss_search_type

2. Modules​

  • Displays a list of DataDios modules.
  • Users can select which modules will have search enabled.
    Modules

3. Users​

  • Displays a list of users within the tenant.

  • Each user is shown with:

    • FIRST NAME
    • LAST NAME
    • USER ID

  • This option specifies which users will have the search feature enabled.

uss_configuration

Submission​

  • After configuring the settings, click the "SUBMIT" button.
note

Once the form is submitted, it cannot be updated.

For additional support or advanced features, contact the DataDios support team.

Queue Configuration​

Overview​

The Queue section sets the tenant's default queue — the message queue DataDios publishes entity catalog events to.

This is not only a preference. Saving it does two things immediately: it provisions the entities_catalog queue on the data source you choose, and it schedules the background consumer that drains that queue into the catalog. Until the setting is saved, data source syncs publish nothing and the entity catalog stays empty, with no error to explain why.

Before you start​

  • Register a queue data source first, from the Data sources page. PGMQ is the supported queue connector, and it needs no connection parameters.
  • Only the tenant's primary administrator — the first administrator created for the tenant — can change this setting. Everything downstream connects to the queue as that user, so a different administrator could otherwise select a data source the primary administrator cannot reach, and every later publish would fail.
  • Open Manage → Configuration and select the Queue tab.
  • The tab is directly linkable at /manage/configuration?tab=queue.

Configuration Options​

  1. Default Queue
    • Lists every registered data source whose category is Queue.
    • Select one and click SAVE.
    • Once saved, the page shows which queue is currently in use. Saving again is only needed if you move to a different queue data source.

Troubleshooting​

What you seeWhat it means
The picker is empty and no queue is shownNo queue data source is registered in this tenant. Add one from Data sources first.
The picker is empty but a queue is shown as in useThe queue is configured, but your account cannot see that data source. Any administrator can read the setting; only the primary administrator can change it.
SAVE is disabledEither your account is not an administrator, or the selected queue is already the one in use.
Saving fails without an explanationThe most common cause is that your account is not the tenant's primary administrator. It can also mean the selected data source is not reachable as a queue.