How Quality Check Ownership Works
This page covers the behavior of the Owner field on a quality check in detail. For a lighter conceptual overview, see Introduction. For step-by-step actions, see Change Check Owner and Bulk Change Check Owner.
The field
The Owner field on a quality check identifies a single user who is responsible for the check. Every check has exactly one owner at any time. The field appears in the Edit Check form, in the Bulk Edit Checks modal, in the filter panel of every check list, and in the check's History.
Ownership is independent of the last editor of the check: editing a property does not automatically transfer ownership unless one of the specific transfer rules described below applies.
Defaults at creation time
Who owns a check when it is created depends on how the check came into existence:
- AI Managed (inferred) checks are owned by the
Qualyticsuser. The user is rendered with the literal labelQualyticsin every owner dropdown and filter, and is pinned at the top of the list. - Authored checks default to the user who creates them. If the Owner dropdown in the Edit Check form is left unchanged, the current user is recorded as the owner on save. Authored checks can also be created with an explicit owner: any user with at least the Drafter team permission on the target container's datastore can be selected.
The owner is always a single user. Setting "no owner" is not possible for Authored checks; for AI Managed checks, the owner stays Qualytics until one of the transfer rules below applies.
Transferring ownership
Ownership can change in three ways. Two of them are explicit user actions; the third happens automatically when certain edits are saved.
Explicit transfer (Edit form or Bulk Update)
A user with the Author team permission on the datastore can open an existing check, choose a different user from the Owner dropdown, and save. The new owner must have at least the Drafter permission on the same datastore, and users without that permission are not selectable. The same dropdown is available in the Bulk Edit Checks modal, which applies the chosen owner to every selected check in one save.
Transfer away from Qualytics is one-way in the UI
Once an AI Managed check's owner is transferred from Qualytics to a regular user, the Edit Check form disables Qualytics as a selectable owner. The inline warning "Once transferred, ownership cannot be returned to Qualytics" makes this explicit in the dropdown.
Implicit transfer (editing an AI Managed check)
When an AI Managed check is still owned by Qualytics and a user edits any of its assertion properties (the rule-specific properties payload, coverage, filter, or fields), ownership transfers to the editor on save. The same edit flips inferred from true to false and converts the check to Authored, so future Profile runs no longer replace it.
Editing organizational fields only (description, tags, additional metadata, status, anomaly message field) does not transfer ownership and does not convert the check.
Drafter activation transfer
When a check is moved from Draft to Active, the platform verifies that the current owner has at least the Author permission required to manage an Active check. If the current owner does not have the Author permission, ownership is transferred to the user who activates the check. This prevents an Active check from being owned by a user who cannot edit it.
Permissions
| Action | Required permission on the check's datastore |
|---|---|
| See the Owner field | Viewer |
| Be selectable as an owner | Drafter |
| Change the owner (explicit transfer) | Author |
| Activate a Draft check (may trigger transfer) | Author |
The owner dropdown is populated with the users with at least the Drafter permission on the datastore. Users without that permission are filtered out and cannot be assigned ownership, even by an Author. See Team Permissions for the full permission matrix.
Notifications
Whenever a check is updated, the platform creates an Ownership in-app notification for the user currently listed as owner, unless the updater is the owner. The notification has the form:
{updater name} updated a check you own
#{check id}• {rule title}
Clicking the notification opens the affected check.
A few specifics:
- Self-edits do not notify. Editing your own check does not generate a notification.
- Checks owned by
Qualyticsnever notify. No in-app notification is created when the owner is theQualyticsuser; updates on AI Managed checks are silent until ownership is transferred to a regular user. - Implicit and Drafter transfers do not notify. When ownership changes as part of the same save that produced the notification trigger, the new owner does not receive a notification for that save. The next update by someone else does.
See In-App Notifications for how Ownership notifications appear in the bell-icon list alongside other notification types.
History tracking
Every change to the owner is recorded in the check's History section, alongside property edits, coverage changes, filter updates, tag changes, and status transitions. The timeline shows:
- Who made the change.
- When the change happened.
- The previous owner and the new owner.
Implicit transfers (from Qualytics to a regular user) and Drafter activation transfers are surfaced explicitly, so it is clear when ownership moved automatically.
Owner, Default Anomaly Assignee, and Assignees
Three related concepts are easy to mix up. Here is how they differ:
| Concept | Lives on | Cardinality | What it does |
|---|---|---|---|
| Owner | Quality check | One user | The person responsible for the check itself. Used for filtering checks by owner and for ownership notifications. |
| Default Anomaly Assignee | Quality check | One user | The user that anomalies produced by the check are auto-assigned to at creation time. |
| Assignees | Anomaly | Many users | The users actually responsible for resolving the anomaly. Editable per anomaly. |
The chain reads: a check has one owner and one default assignee; when the check produces an anomaly, that default seeds the anomaly's assignees list, which can then be expanded or narrowed independently.
Filtering by owner
You can narrow any check list to a specific owner in two ways:
- The Owner filter. A dropdown in the filter panel that lists every user with at least the Drafter permission on the datastore, with the
Qualyticsentry pinned at the top. Selecting one user narrows the list to checks owned by that user. Available on every per-datastore check tab and on the global checks explorer. - The Owned subtab. A one-click shortcut to "checks I own", available under both the Active and Draft parent tabs of every check list. Selecting it sets the owner filter to your user automatically.
Both work alongside the other check filters (rule type, status, tags, coverage, etc.), so you can layer them. For example, combine "owned by me" with status Active to narrow the list to your live checks.