Fides 2.80.0 release notes

• 2.80.0: March 3, 2026

Helios

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

• Data Steward Role: Organizations can now delegate data stewardship responsibilities without granting full admin access. The new Data Steward role gives users the ability to link and unlink integrations to systems, review monitor results, and act on IDP monitor actions — while keeping all other administrative functions restricted. This is ideal for teams that need subject-matter experts to manage their own systems and review classification results without the risk of broader configuration changes.
• Action Center Performance:
  • Optimized Database Indexes: New targeted indexes on leaf resources and ancestor lookups significantly reduce query time for tree operations, resulting in faster load times for customers with large datastores. For deployments with over 1 million staged resources, index creation is deferred to avoid blocking upgrades.
  • Cursor-Based Pagination: The resource tree now loads incrementally using cursor-based pagination with a bottom-up query strategy, replacing the previous approach that could struggle with large result sets. The action center stays responsive even for datastores with hundreds of thousands of fields.
• Action Center UI Improvements:
  • Users can now toggle visibility of ignored and active items directly from the action center via a new page settings menu, making it easier to focus on actionable results without losing track of previously reviewed items.
  • The monitor fields screen now uses dropdown filters, replacing the tree filter component for a faster, more intuitive way to narrow results.
• System-Integration Linking Refactor: Systems can now be linked and unlinked from integrations directly within the Integrations page. Deleting a system in Fides will no longer cascade-delete the associated integration and dataset configuration — the link is now managed independently, so teams can safely reorganize their system inventory without losing integration setup work. Existing links are automatically migrated with no action required.
• Bug Fix: Fixed the data map report drawer briefly showing stale details from a previously selected system before loading the new one.

Lethe

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

• Privacy Request Diagnostics: Support teams can now export a diagnostics summary for any privacy request to quickly troubleshoot issues without needing direct database access. The new GET /api/v1/privacy-request/{id}/diagnostics endpoint returns a structured JSON report with execution metadata, task statuses, and timing information — with no PII or secrets included, making it safe to share in support tickets.
• Property-Based DSR Scoping: For customers managing multiple properties (websites, apps, or brands), DSR execution can now be scoped to only the datasets relevant to a specific property. Privacy requests submitted from one property won't unnecessarily touch datasets belonging to other properties, reducing execution time, lowering infrastructure costs, and limiting the blast radius of each request. Controlled by the FIDESPLUS__DSR_PROPERTY_FILTERING__ENABLED feature flag (enabled by default). DSRs submitted without a property_id continue to process all datasets with no change in behavior.
• Policy Management:
  • Administrators can now delete DSR policies they no longer need via DELETE /api/v1/dsr/policy/{policy_key}. The endpoint includes a safety guard that prevents deletion of policies referenced by existing privacy requests, so there's no risk of orphaned request data.
  • Privacy request creation now generates a policy_evaluated audit log entry, giving compliance teams a clear record of which policies were considered when a request was submitted.
• Privacy Center:
  • The privacy request submission and identity verification experience now uses dedicated full-page routes instead of a modal overlay, providing a cleaner user experience that should reduce duplicate request submissions.
  • Custom privacy request fields now preserve their configured display order after saving. Previously, the ordering could be lost due to how the database stores JSON objects. Configs created before this change maintain their existing behavior.
  • Fixed the property endpoint rejecting visitors from regions with sub-region geolocations not in the PrivacyNoticeRegion enum. Visitors from these locations will no longer see a 422 error.
• Bug Fixes:
  • Long-running privacy requests (such as those using polling connectors) now show accurate, complete status in the UI. Previously, the execution log limit could cause the UI to show incomplete task statuses for requests with many execution steps.
  • Fixed an issue where privacy requests waiting for an async webhook callback were being incorrectly marked as errored by the periodic task requeue job. Requests using callback-based connectors will no longer be prematurely failed.

Janus

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

• FidesJS External ID: Customers can now link consent preferences to their own user identifiers, enabling cross-device and cross-session consent continuity. The new fides_external_id option lets you pass a custom user ID (e.g. your application's logged-in user ID) that is stored in the Fides consent cookie and sent with all privacy-preferences and notices-served API calls. The ID can be set at initialization via options or overrides (query param, cookie, or window), in the Privacy Center via the FIDES_EXTERNAL_ID environment variable, or at runtime after a user logs in via the new Fides.setIdentity({ external_id: "user-123" }) API.
• Consent v3 APIs:
  • A new FIDES__CONSENT__CONSENT_V3_ENCRYPTION_ENABLED setting allows disabling column-level encryption for v3 consent records. Encryption remains enabled by default and is the recommended configuration. This is primarily useful for development and debugging workflows.
  • The propagation policy cascade_down_all_cascade_up_optin has been renamed to cascade_down_all_cascade_up_opt_in_all_opt_out_conservative to better reflect its behavior. If you are referencing the old policy key via API, you will need to update to the new key.
  • Fixed v3 privacy preferences GET endpoints not returning custom meta fields.
• Reporting: The historical privacy preferences report now includes a received_at timestamp, making it easier to distinguish when a preference was actually received versus when the record was created. This is valuable for audit trails and compliance reporting where timing precision matters.

Integrations

• PayPal SaaS Connector: Customers using PayPal can now fulfill DSR access requests through Fides. The new connector supports Invoice Search and Vault Payment Tokens endpoints, enabling automated retrieval of user data from PayPal for access requests.
• Bug Fix: Bazaarvoice erasure requests no longer fail on 409 conflict responses, which could occur when an erasure was already in progress.

Fides core

• SSO Configuration Enhancements: Customers using custom SSO providers with non-standard configurations can now connect without workarounds. The custom SSO provider modal now supports configurable scopes, custom email field paths (including nested JSON paths like profile.email), and the ability to toggle email verification requirements. Existing SSO configurations are fully backward compatible — all new fields are optional and default to previous behavior.
• Removed:
  • The standalone Connection Manager page has been removed from the Admin UI. All integration management functionality is available on the Integrations page, which has fully replaced this view. If your team has bookmarks or documentation referencing the Connection Manager, those should be updated to point to the Integrations page.
  • Manual Process (manual_webhook) is no longer available as a new integration type. Existing Manual Process integrations continue to function normally. This reflects the shift toward the improved manual task workflows that have replaced this older integration type.
• Other:
  • Privacy experience descriptions now support unordered lists (<ul> tags), giving customers more formatting flexibility when writing experience copy.
  • Fixed a theme issue that caused checkboxes and other form components to not render correctly on some pages.
  • Bumped several Python dependencies (Jinja2, pg8000, urllib3, cryptography, Snowflake connectors) to their latest compatible versions for security and stability.

Notes

This release includes five database migrations. The system-integration linking migration is flagged as high-risk due to the structural change from a foreign key to a join table — existing links are automatically migrated, but we recommend testing in a staging environment first.