Faculty application repeatedly rejected with no issues listed

[grazia-appload]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

Faculty application repeatedly rejected with no issues listed
Hello,
I am applying for GitHub Education as Faculty, but my application keeps being rejected.
I have already addressed all the issues that were previously reported:

• my full name matches my GitHub public profile;
• my billing information matches my legal name;
• my institutional school email address is verified;
• I selected Faculty as the application type;
• I submitted an official school document confirming that I am a teacher employed under a permanent contract;
• I also submitted a September 2026 payslip issued by the Italian Ministry of Education, showing my current employment status.
  In earlier attempts, GitHub provided specific reasons for the rejection, which I addressed before reapplying.
  However, my latest applications are rejected with the following message:
  “We were unfortunately not able to verify your academic status. Please address the following issues and apply again.”
  The problem is that no issues are listed at all, so I no longer have any indication of what needs to be corrected.
  In addition, the rejection is issued almost immediately after submitting the application, usually within a very short time.
  I have therefore checked and updated all the information available to me, but the application continues to be rejected without any actionable feedback.
  Could someone please advise whether this may be a verification issue and what I should do next to complete the Faculty verification?
  Thank you very much for your help.

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

[sunmeat]

Hi @grazia-appload, thanks for the detailed write-up and for listing what you've already checked.

A rejection with an empty issue list, issued within seconds, suggests the application is being declined by an automated check that has no specific reason to report (or that a previous rejection is affecting later attempts). Community members can't see or override verification decisions, so the most reliable path is GitHub Education support. Before escalating, a few things are worth re-checking, since they are the most common causes of silent rejections.

1. Re-check the document itself

Reviewers look at the document image, not only your profile data. Make sure that one image or a combined set of images clearly shows all of the following:

• Your full name, exactly as in your GitHub profile and [billing information](https://github.com/settings/billing/payment_information).
• The full name of your school written out in text. A logo alone is not enough.
• Evidence of current employment as a teacher (for example, a dated employment certificate or a staff ID valid for the current school year).

Important

If the document is not in English, GitHub's guidance is to photograph the original next to an English translation in the same submission. Documents in Italian submitted without a translation are a common reason for rejection.

Also consider:

• Payslips may be hard to verify automatically because they often don't show the school name or a clear teaching role. They work best as a supplement to an official employment certificate, not as the primary document.
• Redact sensitive details (salary, tax ID, bank data) that aren't needed, but do not crop out your name, school name, or date.
• Use a sharp, well-lit capture with no glare, and avoid heavily compressed screenshots.

2. Make sure the account state is clean

1. Confirm your name in [Profile settings](https://github.com/settings/profile) and billing information is identical to the document (no abbreviations or nicknames).
2. Confirm your institutional email is verified under [Emails](https://github.com/settings/emails).
3. Sign out and back in after changing profile or billing data, then reapply.
4. Check that you're applying under Teacher/Faculty and that location services or camera permissions (if requested) aren't blocked in your browser.

3. Pause repeated submissions

Warning

Reapplying many times in a short period with the same documents can keep producing the same automated result and may make it harder to get a manual review. Change something concrete (for example, add a translated, school-name-visible document) before the next attempt.

4. Request a manual review from GitHub Support

If everything above checks out and the rejection still lists no issues, open a ticket through the [GitHub Education support form](https://github.com/proxy/support.github.com/contact/education) and include:

Subject: Faculty application rejected with no listed issues - request manual review

GitHub username: grazia-appload
Application type: Faculty / Teacher
Country / institution: Italy - [school name]
Date(s) of rejection: [dates]
Message received: "We were unfortunately not able to verify your academic status.
Please address the following issues and apply again." (no issues listed)
Documents submitted: [employment certificate, payslip, translation if any]
Already verified: profile name, billing name, institutional email
Request: Please review my application manually and advise what is missing.

Note

This thread was submitted as a Bug report, and the empty-reason rejection is worth flagging as such. Including the exact message and timestamps in your ticket helps the team investigate whether the automated check is failing without returning feedback.

Tip

Don't post ID documents, payslips, or personal data in this public discussion. Share them only through the support form if requested.

References

• [Apply to GitHub Global Campus as a teacher](https://github.com/proxy/docs.github.com/en/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)
• [GitHub Education support](https://github.com/proxy/support.github.com/contact/education)
• [GitHub Education community discussions](https://github.com/orgs/community/discussions/categories/github-education)

I'm not a GitHub staff member, so please treat this as community guidance and confirm the current requirements in the official docs. Good luck, and consider posting an update if support resolves it.

[grazia-appload]

Update:
I tried to contact GitHub Education Support as suggested, but when selecting “GitHub Education application not approved (teacher)”, the support form displays the following message:
“Individual manual reviews and status updates are no longer provided.”
It redirects users back to the GitHub Education Community.
So at the moment I seem to be stuck in a loop:

• the application is rejected almost immediately;
• the rejection contains no issues to address;
• Education Support does not provide individual reviews and redirects me back here.
  I have already verified my profile name, billing information, institutional email, Faculty application type, and submitted documentation showing both my teaching role and current employment.
  Is there any other way to resolve an application that is being automatically rejected without any reason being provided?