Currently project browser access is controlled by the "Administer modules" permission. This gives full access to all project browser functionality.
It might be useful for "power users" to be able to browse modules, without the ability to install them.
Grant a user "Administer modules" permission. Note they have access to the "Install" button (if enabled).
Add new permission, "Browse modules" users with this permission would have access to the "Extend->Browse" page, but the install functionality would be hidden or disabled.
Some thought would be needed to the menu structure that would be revealed to users with this permission. The "Extend" menu would normally be hidden in this case, so either the Extend menu would need to be enabled in this case, or the project would need to be placed in an alternative place in the menu structure. If the Extend menu was enabled for users with "Browse modules" permission would need be done in a way that doesn't give access to the core modules page.
I think some discussion is needed to agree the best path forward.
Active
2.0
Code
adding as core-mvp because we at least need a decision one way or the other by then
Closing as a duplicate of ✨ Create granular on a per plugin basis Active , which seems to cover much the same territory.