You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update access_notifications.md to include instructions on how to access Notifications page when inbox icon is not present. #45464
What part(s) of the article would you like to see updated?
In the "Reviewing all of your subscriptions" section of the webpage, Step 2 requires the user to be on the Notifications page (https://github.com/notifications). Thus, Step 1 needs to lead the user to that page. Step 1 contains the aforementioned reusable, which provides the following instructions:
(screen capture included above due to relevant icons/images)
The problem with these instructions is that it is possible for a user's GitHub webpage to not show the inbox icon. The user cannot click an icon that is not present, so for users in this situation alternate instructions should be provided to lead them to the Notifications page successfully.
Additional information
For context about what circumstances result in the inbox icon not showing in the GitHub website's UI, here is the explanation as described by the GitHub Support member who helped me troubleshoot my lack of an icon:
Thanks for the additional information. I was able to reproduce the behavior on my side.
The Notifications button is removed from the header when On GitHub/web notifications are disabled for the account. This also explains why the button appears briefly during page load and then disappears once your notification settings are applied.
You can enable it from Settings > Notifications by enabling On GitHub notifications for the notification types you want to receive. Once enabled, the Notifications button should remain available in the header.
My earlier statement that the button should always be present was incorrect - apologies for the confusion, and thanks for helping us narrow this down.
Hi @beandrake, I've reviewed this and I think the PR@shamu45678 has proposed is a suitable solution ... I wanted to give you a chance to review it before I went ahead and merged it, as the original reporter. Thank you for your patience 🙇
Activity
subatoi commentedon Aug 11, 2026
Hi @beandrake, thanks for reporting this—we'll investigate and come back to you as soon as we can
subatoi commentedon Aug 17, 2026
Hi @beandrake, I've reviewed this and I think the PR @shamu45678 has proposed is a suitable solution ... I wanted to give you a chance to review it before I went ahead and merged it, as the original reporter. Thank you for your patience 🙇
beandrake commentedon Aug 17, 2026
Thank you, @subatoi. @shamu45678's PR looks like it addresses the issue nicely, so I'm happy to give it my stamp of approval.
subatoi commentedon Aug 18, 2026
Great, thank you! I'll get that merged and you should see this issue close with automation.
Thank you very much for raising an issue, and for your interest in the GitHub docs 🙇