Add Toggle to search for Users Locally vs Globally

[nickforsythbarr]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

When managing teams and such we have to use a global search and most of the time this isn't what we want, we just want to fuzzy search over existing members. Infact a global search in every context is risky and dangerous.

Please provide an ability to toggle local | global search. and or a button which adds that is:member filtering prefix would work too.

thanks.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[nickforsythbarr]

discussed separately here and here

[yatharthbhatt]

This is a valid usability concern. Defaulting to a global user search inside a private team management context increases the risk of accidental data exposure or inviting the wrong external user.🧮 Why the Current Layout is RiskyWhen adding or managing team members, the input field uses GitHub's universal user directory. If a maintainer types a common name or makes a typo, the system displays millions of public GitHub accounts. Clicking the wrong name instantly invites an external stranger into a sensitive team or organization context.🛠️ The Proposed Solution: Contextual Toggle or FilterGitHub needs to restrict the search boundary by introducing one of two features:A Local/Global Toggle: A simple UI switch next to the search input that restricts queries to Local (users already inside the Organization or Enterprise) by default, requiring a conscious click to switch to Global.Auto-Injected Filter Prefix: Automatically inject the is:member or org:orgname search prefix into the input box when a user clicks the team management search bar.💡 Temporary Search ShortcutUntil a UI toggle is built, you can manually force a local fuzzy search in the team management bar. Type your organization's name directly into the search string using this syntax to filter out global users:org:YourOrgName username

[mohammadrezwankhan]

The toggle would be useful, and the API model suggests a clear way to implement it without exposing a broader directory than necessary.

For a “Local” mode, the server can search the already-authorized membership set returned by GET /orgs/ORG/members?per_page=100 (or the team-specific GET /orgs/ORG/teams/TEAM_SLUG/members?per_page=100) and filter the returned logins/display names locally. Both endpoints are paginated, so the UI should not treat the first page as the complete member list. The relevant permissions and behavior are documented in organization members and team members.

“Global” can keep the current directory search. The important safety detail is that changing from Local to Global should be explicit and visually persistent, and an invite flow should show the organization/team context before submission. A membership check such as GET /orgs/ORG/members/USERNAME can be used as a final server-side guard, but it should not replace the scoped search.

That gives maintainers an immediate workaround for integrations while preserving your requested product change: default to the smallest context, offer an explicit Global toggle, and never make a global result look like an existing member.