Allow GitHub Enterprise Cloud administrators to configure enterprise-scoped search as the default search behavior

[paridhiarya]

🏷️ Discussion Type

Product Feedback

Body

Summary

GitHub Enterprise Cloud currently defaults searches from the top search bar to all of GitHub, even when users are operating within an Enterprise Managed Users (EMU) enterprise context.

We would like an enterprise-level setting that allows administrators to make enterprise-scoped search the default behavior.

Problem

In large EMU environments, users primarily search for internal repositories, code, and documentation within their enterprise. However, the current default global search behavior mixes public GitHub results with internal enterprise results, making repository discovery less efficient.

This creates friction for developers who are trying to locate enterprise-owned repositories across multiple organizations.

Current Behavior

• The GitHub top search bar defaults to Search all of GitHub.
• Enterprise users must manually add filters such as enterprise:<enterprise-slug> or use pre-scoped search URLs.
• There is currently no enterprise admin policy or setting to make enterprise-only search the default.

Requested Capability

Provide an enterprise-level setting such as:

Default search scope:
- Current enterprise
- Current organization
- All GitHub

When enabled, searches initiated from enterprise or organization contexts should default to enterprise-scoped results, while still allowing users to expand to all GitHub when needed.

Why This Matters

• Improves discoverability of internal repositories and assets
• Reduces noise from unrelated public results
• Provides a better experience for large GHEC and EMU customers
• Aligns search behavior with enterprise user intent
• Reduces reliance on bookmarks, manual filters, or custom pre-scoped URLs

Notes

This request is not asking GitHub to block public repository visibility for EMU users.

The ask is to provide a configurable default search scope so enterprise-owned content is prioritized by default, especially for large GitHub Enterprise Cloud environments.

[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. ⭐