Skip to content

Getting Started with Enrichment

Enrichment is Qualytics writing its findings back into your own infrastructure. An enrichment datastore receives those findings and appears in the same tree as every other datastore. It can contain computed assets, run operations, and be referenced in flows. When a source datastore is linked to it, it becomes that source's enrichment destination. Scan, Materialize, and Export write their outputs there so they can be queried, audited, and read by other systems.

This section covers both sides of the link: the settings on the source datastore and what its operations write, and what the destination shows and can do. Linking needs at least the Member role and the Editor team permission on the source datastore; unlinking needs the Admin role.

Deep Dive

  • Introduction


    What an enrichment datastore stores, why to link one as a destination, and what each operation writes.

    Introduction

  • How It Works


    Settings, automatic sync and profile after each write, display names, lineage, last write, and unlinking.

    How It Works

  • Enrichment Purposes


    The six purposes, where the badge appears, and what a written container shows.

    Purposes

  • Enrichment Outputs


    Physical names and columns of Scan outputs, remediation snapshots, and materialized copies.

    Enrichment Outputs

  • Export Outputs


    Columns of the exported anomalies, checks, field profiles, and check templates, with SQL for unpacking their JSON.

    Export Outputs

  • Schema Changelog


    Column additions, removals, and type changes to the outputs a Scan writes, by date.

    Schema Changelog

  • Permissions


    Which roles and team permissions can link, edit settings, unlink, and work inside a destination.

    Permissions


How-tos

  • Link an Enrichment Destination


    Link an existing datastore as the destination, or create one from inside the dialog.

    Link

  • Link on Datastore Creation


    Link or create the destination in the second step of the Add Datastore page.

    Link on Creation

  • Unlink an Enrichment Destination


    Remove the link from a source datastore.

    Unlink

  • View the Relationship Diagram


    Open the diagram of how the written outputs join one another.

    Relationship Diagram


Reference

  • Supported Connectors


    Which connectors a destination can live on.

    Supported Connectors

  • API


    Link, unlink, change settings, create a destination, and read written outputs programmatically.

    API

  • FAQ


    Where destinations live in the tree, what the badges mean, missing last writes, renamed outputs, and turning off auto-sync.

    FAQ