> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/minor-release/release8.1/release-notes/general-system-settings.md).

# General System Settings

This release introduces new system settings that enhance user control over the application's behavior.

<table><thead><tr><th width="163.54547119140625">Key</th><th width="413.8182373046875">Description</th><th>Impacted Modules</th></tr></thead><tbody><tr><td>lineage.ai.enabled</td><td><p>Configure to enable the Lineage AI build, which enables building lineage for the configured connections using AI. This setting is supported across all supported data source types.</p><p><strong>Parameters:</strong></p><ul><li>Default value: False</li><li>Description: Configure it with true to enable AI Augmented Lineage build on configured connections.</li></ul></td><td>Lineage</td></tr><tr><td>ai.generatedesc.object.metadata.config</td><td><p>Configure which roles are allowed to use AI Generate Description with object metadata.</p><p><strong>Parameters</strong>:</p><ul><li>The default value is selected as ALL.</li></ul></td><td>AI</td></tr><tr><td>msteams.interactive.bot.tenantid</td><td><p>Specifies the unique Directory (tenant) ID for your organization, which is used to identify and authenticate the Microsoft Teams interactive bot in Azure. It ensures that the bot operates within the correct tenant context during configuration and communication.</p><p><strong>Parameters</strong>:</p><ul><li>Provide the tenant ID from the Microsoft Entra ID section of the Azure Portal or from the Configuration settings of the registered Azure Bot.</li></ul></td><td>Notifications</td></tr><tr><td>msteams.interactive.bot.clientid</td><td><p>Specifies the Application (client) ID of the registered bot used for Microsoft Teams integration. It uniquely identifies the bot within Azure Active Directory and is required to establish secure communication between the application and the bot service.</p><p><strong>Parameters</strong>:</p><ul><li>Provide the valid Application (client) ID from the Azure App registration associated with the bot.</li></ul></td><td>Notifications</td></tr><tr><td>msteams.interactive.bot.clientsecret</td><td><p>Stores the secure client secret associated with the Microsoft Teams Bot App registered in Azure. It is used as a credential to authenticate the bot application and enable secure communication with Microsoft Teams services.</p><p><strong>Parameters</strong>:</p><ul><li>When configured, the bot application can successfully authenticate and interact with Microsoft Teams services.</li><li>When not configured or invalid, authentication will fail, preventing the bot from functioning properly.</li></ul></td><td>Notifications</td></tr><tr><td>askEdgi.workspace.download.allowed.roles</td><td><p>Defines which user roles are permitted to download data from the askEdgi workspace. It controls access to the download of outputs generated by analysis and chat, ensuring that only authorized roles can export workspace data.</p><p><strong>Parameters</strong>:</p><ul><li>Specify the roles that are allowed to download data from the askEdgi workspace.</li></ul></td><td>AI</td></tr><tr><td>enable.msteams.interactive.card.notification</td><td><p>Controls whether MS Teams interactive card notifications are enabled for the Question Wall module whenever a question is assigned to them or on subsequent replies. The recipient can respond directly in MS Teams without logging in to the application.</p><p><strong>Parameters</strong>:</p><ul><li>The default value is false.</li><li>If set to true, users receive an interactive card in MS Teams.</li><li>If set to false, the notification sent to MS Teams is a static (non-interactive) card. The recipient can view the information, but cannot reply from MS Teams. To respond, they must log into the application.</li></ul></td><td>Notifications</td></tr><tr><td><p><br><br></p><p>enable.slack.interactive.card.notification</p></td><td><p>Controls whether Slack interactive card notifications are enabled for the Question Wall module whenever a question is assigned to them or on subsequent replies. The recipient can respond directly in Slack without logging in to the application.</p><p><strong>Parameters:</strong></p><ul><li>The default value is false.</li><li>If set to true, users receive an interactive card in Slack.</li><li>If set to false, the notification sent to Slack is a static (non-interactive) card. The recipient can view the information, but cannot reply from Slack. To respond, they must log into the application.</li></ul></td><td>Notifications</td></tr><tr><td>ai.context.tuning.config</td><td><p>Stores configuration values used for AI context tuning. It defines the weighting applied to different ranking and governance signals, helping control how AI-driven suggestions are prioritized and evaluated within the system.</p><p><strong>Parameters</strong>:</p><ul><li>Specifies weights for ranking signals used in AI-driven suggestions.</li><li>Defines governance-related weights to influence compliance and policy-based prioritization.</li></ul></td><td>AI</td></tr><tr><td>dqf.excluded.source.connectors</td><td><p>Specifies the source connectors that should be excluded from the Data Quality Functions (DQF) UI list APIs. It accepts a comma-separated list of connector names and prevents the specified connectors from appearing in the DQF UI where source connectors are displayed.</p><p>Parameters:</p><ul><li>Specify one or more connector names as a comma-separated list to exclude them from the DQF UI list APIs.</li><li>Leave the setting empty to include all supported source connectors in the DQF UI.</li></ul><p>Example:</p><p>dbt,some_other_connector</p><p><br></p></td><td>Data Quality</td></tr><tr><td>share.data.ai</td><td><p>Determines whether askEdgi can share and process physical data values with external AI models. It controls the use of actual data values during AI-powered analysis and enrichment while supporting organizational data governance requirements.</p><p>Parameters:</p><ul><li>When enabled (True), askEdgi can use physical data values for AI enrichment, sample data injection, data quality improvement, logical cross-verification, and thread-level data memory to enhance response accuracy and reduce hallucinations.</li><li>When disabled (False), askEdgi restricts all physical data sharing and operates only on schema metadata. Physical data values are excluded from retrieval payloads, chat memory, and agent tool calls to enforce strict data governance and security controls.</li></ul></td><td>AI</td></tr><tr><td>askedgi.workspace.data.retention_days</td><td><p>Determines the number of days askEdgi workspace data is retained before it is permanently removed from storage. It helps manage workspace storage by defining the retention period for imported and processed data.</p><p>Parameters:</p><ul><li>Specifies the retention period, in days, before askEdgi workspace data is physically deleted from storage.</li><li>The retention period resets only after a successful data import or after a recipe execution completes.</li><li>Default value: 30 days.</li></ul></td><td>AI</td></tr><tr><td>askedgi.workspace.results.retention_days</td><td><p>Determines how long askEdgi temporary analysis results remain available before the system automatically removes them. The retention period is measured in days and applies only to temporary analysis results generated within askEdgi.</p><p>This setting operates independently of workspace data retention settings.</p><p>Parameters:</p><ul><li>Specify the number of days to retain askEdgi temporary analysis results before automatic deletion.</li><li>Default value: 5 days.</li></ul></td><td>AI</td></tr></tbody></table>

### Existing System Settings - Updated

This release includes updates to existing system settings, enhancing functionality to improve data-processing accuracy and operational efficiency across supported modules.

<table><thead><tr><th width="136.27276611328125">Name</th><th width="136.8182373046875">Updated Field</th><th>Updated Field Value</th></tr></thead><tbody><tr><td>download.row.limit</td><td>Description</td><td><p>Defines the maximum number of rows or items that can be downloaded in a single operation across the OvalEdge application. This limit applies to both Simple and Detailed downloads across all table plugins.</p><p><strong>Parameters</strong>:</p><ul><li>Value must be between 1 and 500,000.</li><li>Default Value: 10,000</li></ul><p><strong>Note</strong>: For Data Catalog list pages, the Simple Download option supports a maximum of 10,000 records.</p></td></tr></tbody></table>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/minor-release/release8.1/release-notes/general-system-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.