> 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.1/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons.md).

# License Types and Add-ons

Each connector is equipped with a default license that enables the core functionalities of metadata extraction and data profiling.&#x20;

To enhance connector functionality, additional license features can be selected during connector configuration. The availability of these features depends on the type of license acquired at the time of application purchase.

<table><thead><tr><th width="184.8333740234375">Add-Ons</th><th>Descriptions</th></tr></thead><tbody><tr><td>Auto Lineage</td><td><p>Automatically builds the end-to-end data flow from source to destination using system-generated processing and metadata analysis. It extracts and parses metadata from source code to generate lineage across supported systems.</p><p>To view the list of connectors that support Auto Lineage, click <a href="/release8.1/connectors/introduction-to-connectors/connector-features/lineage/auto-lineage-supported-connectors.md">here</a>.</p></td></tr><tr><td>Data Quality</td><td>Enables rule-based data quality validation, anomaly detection, and reporting across supported data sources. It supports configurable validation functions, incremental rule execution, and dashboard-based monitoring for Data Quality tracking and analysis.<br>To view the list of connectors that support Data Quality, click <a href="/release8.1/data-quality/data-quality-rules/data-quality-supported-connectors.md">here</a>.</td></tr><tr><td>Data Access</td><td>Enables viewing permissions on objects, users, roles, groups, and policies, such as masking and row access, in a catalog-style format. For supported systems, these can be directly modified in the source.<br>To view the list of connectors that support Data Access, click <a href="/release8.1/connectors/introduction-to-connectors/connector-features/data-access/data-access-supported-connectors.md">here</a>.</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
