Fides 2.79.0 release notes

• 2.79.0: February 17, 2026

Helios

Detect and classify global data risks with comprehensive visualization for data mapping and reporting for modern Enterprise.

• Helios v2 (General Availability): The Helios v2 UI is now generally available and the beta flag has been removed. The new interface fully replaces the legacy Data Detection and Data Discovery UIs, which have been removed from the product.
• Okta Monitor (General Availability): The Okta Monitor is now generally available and no longer behind a beta flag. All Okta monitoring functionality — including identity provider discovery, bulk actions on results, and integration with the Helios action center — is now enabled by default for all customers.
• Monitor Deletion Improvements: Deleting a monitor now shows a confirmation modal warning that associated staged resources, datasets, and active tasks will be affected. When confirmed, all associated monitor results are automatically cleaned up, while any systems or datasets that were previously promoted to the data inventory remain intact.
• Asset Reporting: A new Asset Reporting page is now available under Data Inventory that provides a consolidated, cross-system view of all discovered assets including cookies, browser requests, images, iframes, and JavaScript tags. The report supports filtering by asset type, consent status, categories of consent, and locations, along with search, sorting, and CSV export. This makes it easier to get a unified view of your web asset footprint across all monitored systems.
• Website Monitor Fix: Fixed an issue where uncategorized assets (those without an assigned system) could be selected and added from the bulk action menu in web monitor results. The "Add" action is now correctly disabled when any selected assets lack a system assignment.
• System Inventory: The data stewards column in the system inventory table now displays user information in a consistent format, matching how data stewards appear elsewhere in the Admin UI.

Lethe

Enterprise grade privacy request management and processing with a single orchestration layer for DSRs across vendors and systems

• DSR Execution Performance: Significantly improved the performance of graph traversal operations used during DSR execution. The core algorithms have been optimized from O(N²) to O(N+E) complexity, resulting in dramatic speedups for customers with large dataset graphs — for example, a graph with 5,000 collections now processes in ~30ms versus ~27 seconds previously. These improvements are particularly impactful for customers with complex data maps involving many interconnected systems.
• Custom Connector Templates: Added the ability to delete custom connector templates and revert to the Fides-provided default template. This is useful when a custom template is no longer needed or when you want to return to the standard integration behavior after testing customizations.
• Request Manager Improvements:
  • Fixed an issue where duplicate action type tags (e.g., "access" appearing twice) were displayed on privacy requests in the dashboard.
  • The request received date now displays in MM/dd/yy format instead of relative time (e.g., "2 days ago"), with the full date, time, and timezone available on hover.
• Manual Tasks: Consent manual tasks now correctly filter condition field options based on task type. When only consent tasks are configured, fields not applicable to consent requests (such as due_date) are hidden, and the dataset field source option is removed since consent DSRs don't involve data retrieval. When both consent and access/erasure tasks exist, a warning banner explains the limitations.
• Improved Error Messages: Error messages for SaaS integration requests now log the specific unresolved parameter values, making it easier for support teams to quickly diagnose configuration issues.

Janus

High performance consent recording and orchestration for data sharing, built for enterprise data engineering and AI pipelines.

• TCF Compliance:
  • GPP Notice Filtering: GPP (Global Privacy Platform) notices are now filtered from the privacy notice options when configuring TCF experiences. If a TCF experience has GPP notices already assigned, an error alert is displayed. This prevents misconfiguration since GPP notices should not be included in TCF experiences.
  • TCF 2.3 Mobile Compliance: Added the IABTCF_DisclosedVendors property to the TCF mobile data response, aligning with IAB TCF 2.3 CMP specifications. Mobile apps integrating with Fides now have access to the disclosed vendors binary string directly in the mobile data payload, without needing to decode the TC string.
• Consent v3 APIs: Added support for multiple levels of notice nesting in the consent v3 APIs. Previously, only parent/child relationships (2 levels) were supported. The APIs now handle arbitrary levels of notice hierarchy, enabling more flexible consent structures for customers building complex notice trees. A safeguard at 6 levels protects against infinite recursion.
• FidesJS External ID: Added an optional fides_external_id to the FidesJS SDK, allowing customers to pass a custom user ID that is sent with privacy-preferences and notices-served API calls and stored in the consent cookie. The option can be set via init options, overrides (query param, cookie, window), and in the Privacy Center. A new Fides.setIdentity() helper method allows setting the identity after initialization.

Integrations

• Custom Integration Management: Custom integrations are now visually distinguished in the UI with a clear indicator, and a new "Delete custom integration" button allows you to revert to the Fides-provided template when a fallback is available. This makes it easy to identify which integrations have been customized and to roll back changes when needed.
• Google Service Account Authentication: Added a new authentication strategy for Google Cloud Service Account credentials, enabling Fides to authenticate HTTP requests to Google Cloud APIs using service account keys (JWT-based OAuth2 flow). This includes token caching with automatic refresh and configurable OAuth2 scopes per connection.
• Bug Fixes:
  • Fixed an issue where boolean fields (such as "SSH required") were not displaying their pre-selected values correctly when editing an existing integration connection.
  • Fixed an issue where database passwords containing special characters would fail when reused for the readonly database connection. Passwords are now properly encoded.
  • Fixed a connection error for Snowflake integrations using private key authentication without a passphrase. Private keys are now properly converted to the required DER/PKCS8 format regardless of whether a passphrase is present.

Fides core

• SSO Configuration: Additional SSO configuration options are now available, including scopes, fields, and a verification toggle. This gives administrators more control over the SSO authentication flow. Note: this change includes a database migration.
• Password Editing Flow: Password and credential fields now require clicking an "Edit" button before modifying the value, reducing the risk of accidental changes when viewing sensitive configuration fields like API credentials in monitor configurations.
• Scheduled Job Reliability: Added a 5-minute grace period for daily scheduled jobs (such as the GVL cache reload) to prevent missed executions caused by brief scheduler misfires. This addresses an issue observed in production where the default 1-second grace period was too tight.
• Celery Worker Health Check: Added an HTTP health check endpoint for Celery workers, making it easier to monitor worker health in container orchestration environments.
• Bug Fix: Fixed an issue where the "Save" button incorrectly appeared in the taxonomy edit drawer when viewing core (non-editable) taxonomies.