refactor: system user table formatting [ENG-2429]

[speaker-ender]

Ticket ENG-2429

Description Of Changes

Note: Requires BE changes to test.

Updates the BE type definitions to include full data_steward data.
Updates the systems table to display users using the formatUser function in both the cells and the filter.

Code Changes

Steps to Confirm

1. Create or find a system that has assigned data_stewards and view them in the systems page
2. Verify that the data stewards are in the correct format (the same as the data stewards input in the monitor config form) for both the table data as well as the table filter.
3. Check that no regressions in the table functionality have occured
4. Verify that no other tables were effected.

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 11, 2026 2:31pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		Feb 11, 2026 2:31pm

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates the Systems table “Data stewards” column to display users using the shared formatUser helper in both the cell renderer and the filter UI, and updates the BasicSystemResponseExtended API model to represent data_stewards as full UserResponse objects.

Main issue to address before merge: the filter display-name callback currently can crash when the users list hasn’t loaded yet (calls .find on undefined). Also ensure the backend list endpoint and generated types are aligned with the new data_stewards: UserResponse[] shape so the table doesn’t receive username strings at runtime.

Confidence Score: 3/5

• This PR is moderately safe to merge once the Data stewards filter crash and API shape alignment are confirmed/fixed.
• The UI change is small but there is a definite runtime crash risk in the filter formatter when allUsers hasn’t loaded yet, and the data_stewards type change requires strict backend/frontend schema alignment for the Systems list endpoint.
• clients/admin-ui/src/features/system/table/useSystemsTable.tsx; clients/admin-ui/src/types/api/models/BasicSystemResponseExtended.ts

Important Files Changed

Filename	Overview
clients/admin-ui/src/features/system/table/useSystemsTable.tsx	Updates Data stewards column to render/filter via formatUser; current filter display callback can throw when allUsers is undefined (calls .find on undefined).
clients/admin-ui/src/types/api/models/BasicSystemResponseExtended.ts	Changes BasicSystemResponseExtended.data_stewards from string[] to UserResponse[]; requires backend/list endpoint and any consumers expecting string[] to be updated accordingly.
clients/admin-ui/src/types/api/models/SystemResponseExtended.ts	Adds new SystemResponseExtended model mirroring SystemResponse with system_groups; appears consistent with existing SystemResponse connection_configs and data_stewards types.

[greptile-apps]

_{3 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Filter formatter crashes

convertToAntFilters(..., (username) => formatUser(allUsers?.items.find(...))) will throw when allUsers is still undefined/loading because allUsers?.items.find(...) calls .find on undefined. This can crash the Systems table render before the users query resolves; guard the .find call (e.g., allUsers?.items?.find(...)) or otherwise avoid calling .find until items is available.

[greptile-apps]

Additional Comments (1)

clients/admin-ui/src/types/api/models/BasicSystemResponseExtended.ts
Breaking API type change

data_stewards is changed from Array<string> to Array<UserResponse>, which will break any callers still expecting usernames (including the Systems list table and any filtering/serialization paths) unless the list endpoint schema and all downstream uses were updated in lockstep. Make sure the backend GET /system list response actually returns full UserResponse objects here (and regenerate types if applicable), otherwise the UI will mis-render or throw when formatUser reads object fields.

[lucanovera]

Shows first and last name correctly in the table now.