Currently when creating a Global Script (Administration -> Scripts), it is only possible to associate the script with a single host group.

In environments where:

• Hosts belong to a technical group (e.g., Cisco)
• Users are restricted by site-based groups (e.g., Group 1, Group 2, Group 3, etc.)
• Hosts belong to both a technical group and a site group

This creates a limitation:
Even if a host belongs to Cisco, users cannot execute the script unless:

• The script is assigned to a host group they have permission to
• AND they have proper R/W permissions to that group

Because only one host group can be selected in script configuration, administrators are forced to:

• Duplicate the same script for each site host group
• Maintain tens of identical scripts (in this case ~60 groups)
• Manually keep them synchronized

2. Expected Behavior
Allow selecting multiple host groups when configuring a Global Script.

Example:
Script “Restart BGP on Cisco"

Associated host groups:

• Cisco
• Group 1
• Group 2
• Group 3

OR alternatively:
Provide an option:

• Apply to all host groups
• Apply based on host membership only
• OR apply based on technical group, but allow execution if user has permissions to the host via another group
   
  This feature would definitely help when managing large environments.