GitHub for Nonprofits – organization not appearing in application dropdown

[MikeMartijn]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

GitHub Nonprofits

Body

I am trying to apply for GitHub for Nonprofits on behalf of our Dutch nonprofit foundation, Stichting Comité 30 juni / 1 juli Apeldoorn.

Our GitHub organization is:

SCA-verbind

My GitHub username is:

MikeMartijn

I am the sole Owner of the organization.

The issue is that SCA-verbind does not appear in the “GitHub Organization” dropdown in the GitHub for Nonprofits application portal.

I have already followed the official troubleshooting steps:

• confirmed that SCA-verbind is a GitHub Organization;
• confirmed that I am the Organization Owner;
• revoked and reauthorized the “Nonprofits on GitHub” OAuth application;
• granted the OAuth application access to SCA-verbind;
• confirmed that the app was approved under the organization’s OAuth app policy;
• temporarily removed OAuth app access restrictions;
• refreshed and reopened the GitHub for Nonprofits portal;
• repeated the authorization process.

The organization still does not appear in the dropdown.

The organization is not part of a GitHub Enterprise account or Enterprise trial.

Could someone please advise what else could prevent the organization from appearing, or point me to the correct GitHub for Nonprofits support route for further assistance?

Thank you in advance.

Kind regards,
Michael Martijn
Stichting Comité 30 juni / 1 juli Apeldoorn

[Sagargupta16]

The route is the Social Impact support form: https://support.github.com/contact/social-impact (it is the "Contact us" link on GitHub's nonprofits page; sign in as the account that owns the org). Put the org name, that you are the sole owner, and the list of steps you have already run in the first message, so they do not send you back through the troubleshooting page. This forum is community-run and the Nonprofits team does not pick up cases from here.

Your list already covers everything on the troubleshooting page. The one other documented blocker is in the FAQ: an application must use the same organization name throughout, so an org that was renamed cannot go through. If SCA-verbind ever had a different login, say so in the ticket. Enterprise membership or trial is the other listed cause, which you have ruled out.