Organization access not enough to be assigned as reviewer.

[JakubT-LX]

Select Topic Area

Bug

Body

I have an organization role set to have Admin access to all repositories in the organization.
Only one team is assigned this role and it correctly shows in the Organization access tab of Collaborators and teams section in Settings of all repositories.

However, said team cannot be manually assigned as a reviewer for PRs in these repos and it is not automatically assigned as reviewer when PR modifies files listed in CODEOWNERS as owned by this team.

Both manual assignment and automatic assignment when owned files are modified work, if the team is explicitly assigned access to the repository.

My expectation is the team should be able to be assigned as reviewer, even if the access is granted through organization role.

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