fix: website monitor feature flag [ENG-2659]

[speaker-ender]

Ticket ENG-2659

Description Of Changes

Fixes website monitors being displayed in root action center and integrations form

Code Changes

Steps to Confirm

1. Start with web monitor flag enabled
2. Create a website monitor and scan
3. Disable website monitor flag
4. Confirm that website monitor no longer displays in root action center
5. Go to the integration screen and open the add new integration modal
6. Confirm that you are not longer able to pick a website type of integration from the list of options

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	Feb 12, 2026 9:06pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		Feb 12, 2026 9:06pm

[greptile-apps]

Greptile Overview

Greptile Summary

Fixed website monitor feature flag to properly hide website-related UI when the webMonitor flag is disabled. The changes ensure website monitors don't appear in the action center and website integrations are filtered from the integrations form.

Key changes:

• MonitorList.tsx: Updated filter to use availableMonitorTypes as default when no specific monitor type is selected
• SelectIntegrationType.tsx: Added filtering to exclude website category and integrations when webMonitor flag is off
• useIntegrationFilterTabs.tsx: Filters out website tab when webMonitor flag is disabled

Issues found:

• Missing webMonitor dependency in useMemo hook (critical - causes stale closures)
• Import path inconsistency in useIntegrationFilterTabs.tsx

Confidence Score: 3/5

• This PR has a critical dependency array bug that will cause incorrect memoization behavior
• The missing webMonitor dependency in the useMemo hook on line 142 of SelectIntegrationType.tsx is a critical bug that will prevent the filtered types from updating when the feature flag changes, causing stale closures and incorrect UI behavior. The logic otherwise looks correct for hiding website monitors.
• Pay close attention to SelectIntegrationType.tsx - the missing dependency must be fixed before merging

Important Files Changed

Filename	Overview
clients/admin-ui/src/features/data-discovery-and-detection/action-center/MonitorList.tsx	Fixed monitor type filtering to use all available monitor types when no specific type is selected
clients/admin-ui/src/features/integrations/add-integration/SelectIntegrationType.tsx	Added webMonitor flag filtering to hide website category/integrations when flag is disabled
clients/admin-ui/src/features/integrations/useIntegrationFilterTabs.tsx	Filters website tab from integration tabs when webMonitor flag is disabled

_{Last reviewed commit: 6415bae}

[greptile-apps]

_{3 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

inconsistent import path - use ~/features/common/features instead of ~/features/common/features/features.slice to match the pattern used in SelectIntegrationType.tsx and other files in the codebase

Suggested change

	import { useFlags } from "~/features/common/features/features.slice";
	import { useFlags } from "~/features/common/features";

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[greptile-apps]

Additional Comments (1)

clients/admin-ui/src/features/integrations/add-integration/SelectIntegrationType.tsx
missing webMonitor dependency - the filteredTypes memo depends on webMonitor flag but it's not in the dependency array

  }, [searchTerm, selectedCategory, webMonitor, allIntegrationTypes]);

[gilluminate]

This is working for me locally. However, there might a follow-up needed, since I can get to deep link website assets after the flag has been disabled. The following route still works: pages/data-discovery/action-center/website/[monitorId]/[systemId]/index.tsx. Since that's probably always been the case, it likely isn't super urgent.

[speaker-ender]

This is working for me locally. However, there might a follow-up needed, since I can get to deep link website assets after the flag has been disabled. The following route still works: pages/data-discovery/action-center/website/[monitorId]/[systemId]/index.tsx. Since that's probably always been the case, it likely isn't super urgent.

Yes, I called out some other gaps as well that need to be closed at some point.