As organizations grow, maintaining access and ownership for every individual user becomes a bottleneck. We are excited to introduce Teams—a new way to mirror your company’s real-world structure directly within the platform.

What’s new?

You can now group users into Teams to manage permissions and ownership once — and apply them automatically to everyone in the group.

  • Onboard new users faster with instant, team-level access
  • Update permissions for an entire team in one action
  • Clarify ownership across Domains, Assets and Incidents
  • Built to reflect how your teams actually work

👉 Check this document to learn more.

Version:v603


Sifflet now automatically synchronizes your account timezone with your local browser timezone upon first login.

New users no longer need to manually select a timezone; Sifflet detects your browser’s settings to ensure all incident data and schedules are displayed in your local time.

Impact on Existing Users: If you haven’t previously updated your timezone in your profile settings, your account will now automatically match your current browser timezone.

Manual Overrides: You still have full control to manually change your timezone at any time via the User Profile icon in the top-right corner of the Sifflet application.

Version:v599

In Sifflet, we’ve started improving the Lineage experience! You can now navigate your data structures more easily—no more scrolling through endless lists to find the right data point. This is just one of many enhancements we’ll be rolling out in the future.

What’s New?

Column Search: Quickly find specific columns within any table using the new search bar.

Table Pagination: For tables with extensive schemas , we’ve introduced pagination. You can now flip through pages of columns easily using the new navigation arrows at the bottom of the drawer.

App Version: v598

✨ What’s new

You can now connect Jira using OAuth, alongside the existing authentication method. OAuth offers improved security and reliability.

👉 Check this document to learn more.

App Version: v590

We are excited to launch Subdomains, which provide hierarchical organization and finer access control across your Parent Domains. This helps teams stay structured, manage access complexity, and ensure specific data assets are only visible to the relevant users.


🚀 Key Benefits

  • Granular Access: Limit access to specific assets and users within a large domain.
  • Hierarchical Structure: Organize complex domains (e.g., "Marketing" divided into "Brand Marketing" and "Digital Marketing").
  • Streamlined Management: Simplify domain maintenance by delegating ownership to smaller units.

You can now enforce more predictable data standards with our Static Threshold option for Metadata Freshness monitors (update-time-gap-based freshness). Instead of relying solely on dynamic, machine-learning-driven deviation, you can set a fixed, maximum (and/or minimum) acceptable time-lag (e.g., "Alert me if the table's metadata hasn't been updated in over 12 hours").

  • This provides greater control and certainty when monitoring business-critical tables with well-defined latency SLAs.
  • Find the new setting within the monitor configuration panel under the "Threshold settings" section.

Defining a static threshold for a Metadata Freshness Monitor.

App Version: v576

We introduced a new event scope option for webhooks called “All events.”

With this setting, the webhook will receive every event generated in Sifflet, regardless of whether the event is linked to a specific monitor, source, or asset.

What’s the difference from the existing scope?

  • Linked events (existing)

    Only sends events related to elements explicitly configured with the webhook — for example, specific monitors or sources selected by the user.

  • All events (new)

    Sends all events across the platform to the webhook URL, without needing to link specific elements. Ideal for users who want a single webhook endpoint to capture everything for centralized processing.

    This can be useful for you if you want to retrieve real-time data about our monitor runs. It also serves as an alternative to our Public API Rules.


We're excited to announce a complete overhaul of Sifflet's lineage! We've rebuilt the entire experience from the ground up to make it easier to digest, more powerful, and far more intuitive to navigate.

This revamp provides a cleaner interface that surfaces more metadata, giving you the full context you need without the clutter.

The new lineage graph.

The new lineage graph.

What’s New?

  • 📈 Easier to Digest, Yet More Powerful: The new UI is designed for clarity. We’ve streamlined the view so you can understand data flow at a glance, while simultaneously surfacing richer metadata for deeper analysis.
  • 🔄 New "Transformation" Nodes: You can now visualize pipeline steps directly within your lineage graph. This includes new, dedicated nodes for processes like Airflow DAGs, giving you a true end-to-end picture of how your data is modified.
  • 🧭 Better Navigation for Complex Graphs: We know lineage can get complicated. The new graph comes with enhanced controls for panning, zooming, and exploring, making it simple to navigate even the most complex data ecosystems.

How to Access It

You have full control. You can switch between the classic view and the new revamped lineage using a dedicated toggle on the asset and incident pages.

The toggle to activate the new lineage experience.

The toggle to activate the new lineage experience.

Coming Soon

We're already working on the next enhancements: collapsible and expandable BI lineage nodes and data product lineage. This will give you even more control to simplify your view and focus on the assets that matter most.

We're excited to announce a major upgrade to our Conditional monitors! We've removed their previous limitations, bringing them in line with all other Sifflet monitors (like Format Validation).

Conditional monitors now support the full suite of Sifflet's powerful monitoring features. This update simplifies monitor configuration and unlocks new data quality use cases.

Key capabilities now available for Conditional monitors:

  • Advanced Joins: Easily join on more than one dataset using Sifflet's standard "join-everywhere" logic, replacing the old custom join code.
  • Incremental Scans: Optimize your monitor runs by scanning only new or changed data.
  • Full Feature Parity: You can now use group_by, where, and threshold settings to build more specific and powerful conditional checks.
Joining datasets for a Conditional Monitor

Joining datasets for a Conditional Monitor

What this means for you:

  • For existing monitors: You can start updating your current Conditional monitors today to leverage these new configurations.
  • For Data Quality as Code (DQaC): The new, expanded configuration is fully supported in our DQaC syntax.

App Version: v567

The Domain Management APIs empowers you to perform full lifecycle management of domains — from creation to deletion — enabling smoother integrations and automation of domain-related operations.

Available Endpoints:

GET /domains — Retrieve the list of all configured domains.
POST /domains — Create a new domain.
DELETE /domains/{id} — Delete a domain by its unique ID.
GET /domains/{id} — Retrieve details for a specific domain.
PATCH /domains/{id} — Update the configuration or metadata of a domain.

💡 Why is this useful?

These new APIs allow developers and platform integrators to manage domains directly through automation or external workflows — without needing to use the Sifflet UI.

We are working on integration domain in our terraform provider that will be available in a few weeks.