Currently, granting Read permission to a template group allows users to see the template and also link that template to hosts they can modify.
 
In multi-team environments this is too broad. We need users to be able to see inherited items/triggers from linked base templates, for example "Generic by SNMP", without allowing them to directly assign those base templates to their own hosts.
 
Requested enhancement:
Separate template permissions into at least:

• View/read template metadata and inherited objects
• Link/assign template to hosts
• Modify template
   
  This would allow centrally managed base templates to be visible for inherited object display while preventing direct assignment by local host maintainers.