GitHub for Nonprofits approved by email, but portal still sends org back to new application flow

[KristianMunsche]

🏷️ Discussion Type

Bug

Body

Hi all,

I’m running into a weird GitHub for Nonprofits issue and want to check whether others have seen the same thing.

Our organization’s GitHub for Nonprofits application was approved by email.

But when I go back to nonprofits.github.com and sign in with the approved account, the flow does not let me claim the free GitHub Team plan for the organization. Instead, it sends me back to the generic “Get started on your application” page.

What I’ve already checked:

• I’m signed into the correct GitHub account
• I’m selecting the correct GitHub organization, i am the owner of the organization
• In the OAuth authorization screen, the organization shows with a green check under Organization access
• The organization is currently on GitHub Free
• The Nonprofits on GitHub OAuth app is authorized
• I also tested removing and re-authorizing access

So the odd part is:

• approval email exists
• org access looks correct
• portal still behaves as if no approved application exists for the org

Has anyone seen this exact mismatch before, where the approval email exists but the nonprofit portal still redirects back into the application flow?

I suspect the nonprofit approval may not have been properly attached to the organization on the backend.

If a GitHub staff member sees this, I’d appreciate confirmation on whether this is a known portal/backend issue.

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