Skip to content

Getting Started with Tags

Tags are labels you create once and apply across your data, such as Finance, PII, or Deprecated. They organize datastores, tables, fields, checks, and anomalies, decide how much each one counts in quality scores and triage, and let Flows and operations act only on what carries them. This page maps the Tags documentation: what each part covers and when to read it.

Understand Tags

Start here to learn what tags do and how they behave before you create or reorganize them.

  • Introduction


    What a tag is in Qualytics and what it is for, in a few lines. Read it first.

    Introduction

  • How It Works


    How tags influence Qualytics: quality scores, check importance, Flows, and operations, how a tag reaches the assets inside a datastore, and what each change does. Read it before tagging a whole datastore or changing a weight.

    How It Works

  • Weight Modifier


    The number behind every tag and the exact math it adds to quality scores and check importance. Read it when a score or an anomaly ranking surprises you.

    Weight Modifier

Kinds of Tags

Read these to tell the three types of tags apart: open to everyone, owned by one team, or imported from a data catalog.

  • Global Tags


    Tags open to the whole workspace, managed by Admins, and how a tag becomes global or stops being global.

    Global Tags

  • Team Tags


    Tags that only one team can find and apply, and what happens to them when the scope or the team's access changes.

    Team Tags

  • External Tags


    Tags imported from a connected data catalog, and which of their settings Qualytics can change.

    External Tags

The Tag Page

Read this when you need to know where a tag is used, or before you move, merge, or retire it.

  • Tag Page


    Each tag's own page: its summary and timeline, the list of every tagged asset, a map of how they connect, and the actions that change many assets at once.

    Tag Page

Plan and Govern

Read these when you design a tag library for your organization or decide who can manage it.

  • Examples


    Real scenarios: focusing a datastore score, routing alerts on personal data, giving a team its own labels, and merging duplicates.

    Examples

  • Best Practices


    Guidelines for a tag library that stays small, consistent, and worth filtering on.

    Best Practices

  • Permissions


    Who can create, apply, and manage tags, by user role and team permission.

    Permissions

Do Something With Tags

The How-tos walk through each task step by step.

  • Manage the tag itself


    Add, edit, delete, or merge a tag in the library.

  • Change the assets that carry it


    Apply a tag, move it to another tag, or remove it from many assets at once.

  • Find a tag


    Filter and sort the Tags list by type, scope, or category.

Look Something Up

  • API


    Manage tags and act on their assets programmatically.

    API

  • FAQ


    Quick answers about inheritance, weights, team tags, and merging.

    FAQ