Skip to content

Quality Check Ownership Introduction

Overview

Every quality check in Qualytics has a single owner: the user responsible for the check. Ownership is recorded directly on the check, shown as the Owner field in the UI and as the owner object on every API read.

Ownership is the answer to a basic question that comes up in any data quality program: who is responsible for this rule? With that answer in place, the platform supports three workflows:

  • Filtering by responsibility. The check list has an Owned subtab that scopes the list to the current user, plus a per-user Owner filter for inspecting any teammate's checks.
  • In-app notifications. When a teammate edits a check you own, you receive an Ownership notification linking back to the check.
  • Audit trail. Every change to the owner is recorded in the check's History, alongside property edits and status transitions.

Why this matters

A check without a clear owner is hard to maintain. Whoever opens it later cannot tell whether someone else is already responsible for it, who to ask about its intent, or whether tweaking it would step on another team member's work. Ownership turns that ambiguity into a concrete attribution and gives teammates a way to coordinate before making conflicting edits.

Ownership also flags which checks are still managed by the platform. AI Managed checks start out owned by the Qualytics user. When a user edits one of its assertion properties (properties, coverage, filter, or fields), the owner changes to the editor and the platform stops managing the check. An Author can also explicitly transfer ownership without editing any assertion property; in that case the new owner is attributed but the check remains AI Managed until an assertion edit converts it to Authored.

The transfer modes at a glance

Ownership changes in three ways. Each is documented in detail on How It Works:

  • Explicit transfer. A user with the Author team permission picks a new owner from the Owner dropdown in the Edit Check form, or from the Bulk Edit Checks modal when handling many checks at once.
  • Implicit transfer. Editing an assertion property (properties, coverage, filter, or fields) on an AI Managed check moves ownership from Qualytics to the editor on the same save.
  • Drafter activation transfer. When a Draft check is moved to Active and the current owner does not have the Author permission, ownership transfers to the user who activated it. This prevents an Active check from being owned by a user who cannot edit it.

Next Steps

  • How It Works

    Full semantics: defaults, the three transfer modes in detail, permissions, notifications, history tracking, the comparison with anomaly assignees, and filtering.

    How It Works

  • Examples

    Production scenarios that show ownership in action: onboarding, handoffs, notification-driven workflows, compliance audits, and Draft promotion.

    Examples