Skip to main content
Go to and click Add product. A wizard guides you through the steps below.

​
Definition

  1. Name your data product (e.g., marketing KPIs).
  2. Add a description (optional).
  3. Set a priority (optional): P-1 for business-critical data, then P-2 and P-3.
  4. Select a domain and a folder (optional). Folders group related data products.

​
Assets

Select the assets that belong to the data product. Use the browser to select or search for specific assets, or use annotations to select assets based on their code definitions. title

​
Owner

The data product owner is a person or team responsible for the data product. Owners see an overview of everything they are responsible for, and who owns critical data downstream. Choose an owner, or click Add a new owner to create one. When you create an owner, you also set how the owner is notified about issues (e.g., which Slack channel). See Creating an owner. title

​
Alerting

Turn on Add an issue alert for this product to get alerts about issues on the product’s assets. If the product has an owner, alerts go to the owner’s contacts unless you pick other targets. If it has no owner, choose where alerts go. title In the alert settings you can:
  • Choose which severities to alert on. By default, the alert covers error and critical issues. Add warn to get alerts about warn-level test issues from dbt, SQLMesh or Coalesce Transform.
  • Include upstream issues that can affect your data product.
  • Get repeated alerts while an issue stays open. This sends more alerts.

​
Creating a data product programmatically

The asset selection you build in the wizard is a membership query. You can also write it directly.
  • Public API: synq.dataproducts.v2.DataproductsService lists products, fetches one with its membership definition, resolves the assets currently in it, and upserts or deletes it. Reading needs a token with SCOPE_DATAPRODUCT_READ, writing needs SCOPE_DATAPRODUCT_EDIT. See the API reference and API scopes.
  • MCP: the data product tools let an AI assistant review what exists, draft a membership query, and save the product once you approve. Reading is covered by read-only consent; saving and deleting need the Governance permission and are confirmation-gated.