GitHub: Organization Authorization

You authorized Git-Zen, but you only see your personal repositories. Your organization’s repositories are missing. The cause is usually OAuth app access restrictions on the organization.

With these restrictions on, an organization owner must approve Git-Zen before it can see the organization’s repositories.

The process has three steps:

1. Request OAuth access
2. Approve OAuth access
3. Clear the Git-Zen repository cache

Request OAuth access

The Git-Zen OAuth user does these steps.

1. In the upper-right corner of any GitHub page, click your profile photo, then click Settings.

   

2. In the left sidebar, click Applications.

3. Click the Authorized OAuth Apps tab.

   

4. In the list of applications, click Git-Zen.

   

5. Next to the organization you want Git-Zen to access, click Request access.

6. Review the information, then click Request approval from owners.

Approve OAuth access

Note

An owner of your GitHub organization must do these steps.

1. In the upper-right corner of GitHub, click your profile photo, then click Your organizations.

2. Next to your organization, click Settings.

3. In the left sidebar, click Third-party access, then OAuth application policy.

   

4. Next to the Git-Zen application, click Review.

   

5. Click Grant access.

Clear the Git-Zen repository cache

Git-Zen caches your repository list. After the owner grants access, click Clear Repository Cache on the Git-Zen Webhooks screen. See A new repository or project is missing.

Other options

If your organization does not allow OAuth apps at all, use a personal access token. An organization can also require approval for fine-grained tokens.

More information

See the GitHub documentation: About OAuth app access restrictions.