Add "access vocabulary FOO overview" permission

IIRC, B was implemented so that a custom/contrib module could easily provide the extra permission. I'm not sure that the use case for that is common enough to be in core. Every permission that is added makes the permission page a bit bigger again...

Not clear the reason to "access" overview - the reason to access overview is only to reorder terms (except lookup) then it fits into mapping to vocabulary form access

> #4: If we can deny access to vocab admin pages without additional permission (no add / edit / reorder permission, no access), all the better.

Being able to just view a list of all terms without any access to change them is a valid use case, e.g. to have a list of things to look at or so. It's also impossible to check anyway, entity access would allow to only grant edit access for specific terms, based on arbitrary conditions. We can't check that for the whole list.

> I'm currently facing such a use case, which is simply:

Yes, but the question is whether your use case is common enough to warrant having those permissions around for everyone :)

Using the hook, if you do want to limit it based on the edit permission for example, you could implement hook_taxonomy_vocabulary_access(), look for $operation 'access term overview' and return forbidden if the user doesn't have administer taxonomy or the edit permission. That's just a handful lines of code and doesn't need any new permissions. But it's not an assumption that works for everyone.

I believe this is sufficiently handled by the Taxonomy Access Fix module.

This provides "view" and "reorder" permissions for each vocabulary. I frequently find this useful in sites we create because we often have a vocabulary or two that only developers, not content admins, should modify, so we want to limit which ones the admins or other roles can see. Also, we sometimes have the use case where the client wants a user role that can only edit certain content, including specific vocabularies. They all need to have access to the vocabulary overview page, otherwise, nothing appears for them to access it via the admin toolbar, but as others have noted here, seeing all the other vocabularies they cannot do anything with is just confusing. Plus, it may show them ones they don't need to know even exist because we are perhaps using them for some kind of functionality that only developers should ever have access to see and modify.

While I kind of wish this was in core without the need for an extra module, I think I agree that this is not necessarily a common use case. And many of our sites don't have vocabularies that the content admins shouldn't be able to modify, so even we don't use it all the time. So it would indeed just add more permissions to the permissions page that may not be needed most of the time.

There's also the Vocabulary Permissions Per Role module if you want to allow certain roles to fully administer only certain vocabularies. So between these 2 contrib modules, you can get whatever you need for taxonomy permissions.