Repository navigation
improve enterprise org authorization, approval and visibility #3409
Description
📝 Provide a description of the new feature
Users on GitHub EMU and other enterprise accounts may need to authorize Gitify’s access to each organization individually, depending on their enterprise policies and authentication method.
For example, users authenticating with a personal access token (PAT) may need to visit [GitHub’s token settings](https://github.com/settings/tokens), select Configure SSO, and authorize the token for each organization.
This can be time-consuming in large enterprises, and the need to authorize organizations may not be obvious. As a result, a user’s Gitify inbox may not populate until they complete these steps.
This issue tracks improvements to make the authorization process clearer and easier.
Relevant Forge(s)
GitHub
➕ Additional Information
No response
Reacted by Aravind Parappil
Activity
[-]improve ux around enterprise org approval[/-][+]improve enterprise org authorization, approval and visibility[/+]aravindparappil46 commentedon Nov 8, 2026
@setchy - For the unauthorized PAT scenario, how do you feel about just showing a warning message?
Example:
When some orgs are auth'ed but some aren't
Accounts page (non-dismissable message)
setchy commentedon Nov 10, 2026
@aravindparappil46 - the mockups look good.
How do you detected a missing organization? I did some timeboxed research recently and found the organization apis to be lacking to provide a similar view to what is available within GitHub's UI
aravindparappil46 commentedon Nov 10, 2026
Referencing this doc.
So just checking that header in each page of the existing https://api.github.com/notifications API's response, really.
setchy commentedon Nov 10, 2026
Sounds good.
On the
Accountspage, I wonder if it should beauth scopesauth scopes- this view originally was intended to catch any token configuration that would reduce the inbox notifs arriving.