I'm seeing an issue where an account which has permissions for a specific 'Feed & Project Group', when the group does not contain any feeds, is not able to view the feeds page, even though it has permission to create feeds within the group.

These are the permissions that the account has, scoped to a Group which has a few projects, but no feeds yet.

The issue resolves itself if I provide the account access to a feed.
As an example here I've assigned Authenticated access to a feed, to show that the /feeds page starts working as intended again.

It also resolves if I use some other means of giving access to a feed, such as using another account to create a feed in the feed group.

Other pages like /packages and /assets also do not work until the account has access to some feed(asset directory included)

Instead of a generic 403 error it should specify that there is nothing to see, unless you have the permission to create something, in which case encourage that instead.

Best regards
Nils Nilsson