Scheduled reminders ignore organization / enterprise-level team repository access

[vanZeben]

Select Topic Area

Bug

Body

Scheduled reminders only recognize repositories where a team has direct repository access. Repositories where write+ access is granted via Organization access or Enterprise access are ignored, despite the team having effective write permissions.

This leads to inconsistent behaviour and significant administrative overhead in larger organizations.

For organizations with:

• Many repositories
• Many teams
• Centralized permission strategies

Requiring explicit per-repo team assignment purely for reminders defeats the purpose of organization-level access controls. Is this limitation intentional, or an oversight in how reminders evaluate repository access?

---

Observed Behavior

When configuring scheduled reminders for a team:

• Repositories appear only if the team is explicitly added under Direct access
• Repositories do not appear if access is granted via:
  • Organization access
  • Enterprise access

This occurs even when the team has write access to the repository (through Organization access), and the team is added to a Pull Request requiring their code review.

---

Reproduction Steps

1. Create a team in an organization
2. Grant the team write access to all repositories via organization-level permissions
3. Open a repository’s Manage access page
4. Confirm the team appears under Organization access (not Direct access)
5. Attempt to configure scheduled reminders for that team

Result:
No repositories available for selection.

6. Explicitly add the same team under Direct access for a repository

Result:
Repository now appears in reminders configuration.

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