feat: Show F3 name in Manage Access user search results#155
Draft
feat: Show F3 name in Manage Access user search results#155
Conversation
…r search Co-authored-by: taterhead247 <26818765+taterhead247@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add F3 name display in Manage Access user search
feat: Show F3 name in Manage Access user search results
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Manage Access user search was displaying
email (First Last), making it hard to identify users since F3 names are how members know each other.Changes
Modal dropdown format (
admin-manage-access-modal.tsx): Already updated to display results as two lines:Falls back gracefully: if no F3 name, shows full name; if no name at all, shows email only.
API (
packages/api/src/lib/user.ts):f3Name,firstName,lastNameare included in the base (non-PII) select, so they're always returned bybyEmailregardless ofincludePiiflag.Test (
packages/api/src/router/user.test.ts): Added test todescribe("byEmail")that creates a user with known name fields and asserts all three name fields plusemailare present in the response.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.