Skip to main content
Go to and click Add owner. A wizard guides you through four steps: Details, Ownership, Alerting and Review.

​
Details

  1. Enter the Owner name (e.g., product analytics).
  2. Under Notification method, add at least one way to reach the owner:
    • Slack: a channel, and optionally Slack users or user groups to mention.
    • Microsoft Teams: a channel, and optionally users to mention.
    • Email addresses.
    • Coalesce Quality users.
The Slack and Microsoft Teams fields show only when that integration is connected. See Slack integration. title
If you want to send alerts to a private Slack channel, you must first type @Coalesce Quality in the private channel and invite the app.

​
Ownership

Choose what the owner is responsible for. You can combine both options.
  • Products: select one or more data products. A data product has one owner. If a product you select already has an owner, the wizard warns you, and the previous owner stops receiving alerts for it.
  • Assets: select assets with filters, or turn on Own all assets to make the owner responsible for every asset in the workspace (e.g., for a data team owner).
title

​
Alerting (optional)

Turn on Add an issue alert for this owner's assets to notify the owner about issues on everything it owns, including assets added later. The alert goes to the owner’s contacts from the Details step, unless you pick other targets. title

​
Review

Check the summary and create the owner.

​
Managing owners programmatically

You can read and change an owner, its notification channels and the alert configuration of its ownerships outside the app. This helps when you review or change alert routing in bulk.
  • Public API: synq.owners.v1.OwnersService covers owners, their contacts and their ownerships. Reading needs a token with SCOPE_OWNERS_READ and SCOPE_OWNERSHIP_READ; writing needs SCOPE_OWNERS_EDIT and SCOPE_OWNERSHIP_EDIT. See the API reference and API scopes.
  • MCP: the owner tools create or update an owner and the assets it is responsible for in one call, including the severities and channels its alerts go to. Reading is covered by read-only consent; writing needs the Governance permission and is confirmation-gated.