Non profit registration #196208
-
🏷️ Discussion TypeHelp needed navigating non profit application and validating an organisation BodyHi I am new to Github and trying to set up an account owned by our non profit to migrate to then apply for a non profit teams account. Currently I have a personal account, then linked it to an organisation I created via the organisation option in the top right options. The non profit application says I need to validate our organisation but I can't find what this means and how to do it. when I try to proceed it says I'm not logged in as the organisation. I really don't know what I'm doing after after many hours, I now have multiple accounts which doesn't help. Would one of you kind people be willing to jump in a discord call while i share my screen and maybe talk me through it? for now I want to get it registered then start looking at the correct format to set out the account. We rescue and rehabilitate hedgehogs in the UK and have a long term passive monitoring station we have built entirely through volunteers. We are a registered charity, so if you work for an organisation that gives time off for charity help you would qualify. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments · 1 reply
-
|
Hi, first of all — you are actually much closer than you think, and what you are trying to do is a very normal setup for charities and volunteer organisations on GitHub. From your description, it sounds like you already completed the most important step:
That is the correct structure. GitHub organisations are always managed through personal accounts, so there is no separate “login as organisation” account/password. The confusing part is usually the nonprofit verification process. What “validate your organisation” means:
When GitHub says you are “not logged in as the organisation,” it usually means:
Try this:
You should see the organisation name at the top left while applying. For your structure:
Example:
Then grant each team access only to their repositories. For moving projects from private personal accounts: So you do not need to recreate everything from scratch. Also, don’t worry about not being technical enough — GitHub terminology is genuinely confusing for newcomers, especially around organisations, owners, teams, and nonprofit validation. Your use case (charity with volunteers and separate projects) is exactly what GitHub Organisations are designed for. Hopefully someone from the community can jump on a Discord call with you, because screen-sharing would probably solve this in 15 minutes. In the meantime, if you reply with screenshots (with sensitive info blurred), people here can usually guide you step-by-step as well. And honestly, your hedgehog rehabilitation and monitoring work sounds fantastic. Good luck getting everything set up. |
Beta Was this translation helpful? Give feedback.

Hi, first of all — you are actually much closer than you think, and what you are trying to do is a very normal setup for charities and volunteer organisations on GitHub.
From your description, it sounds like you already completed the most important step:
That is the correct structure. GitHub organisations are always managed through personal accounts, so there is no separate “login as organisation” account/password.
The confusing part is usually the nonprofit verification process.
What “validate your organisation” means:
GitHub partners with a service called TechSoup / Percent to verify that your cha…