Launchpad Publishing to Clever Playlists

Problem Statement: Currently- there are 4x ways that Launchpads can end up on player screens.

1. The user directly chooses the players from the Launchpad Publishing menu and a new Playlist is generated and auto assigned to said players. (note: you cannot use this method to have it join an existing Playlist or embedded within Layout)

2. Turn off player selection for your templates. Admins/Designers can then assign a Tag to each Launchpad template they create. So when users publish Tagged Launchpads, the Launchpads are routed to Clever Playlist looking for said Tag. (note: you can control which Launchpads are visible to users with Launchpad folder permissions, but this does require setting up the folder structure + cloning multiple Launchpads with unique tags assigned in each folder.)  https://kb.korbyt.com/article/configuring-clever-playlists/

3. Turn off Launchpad player selection AND do not Tag the Launchpad. When users publish, Admins can then manually choose to include the published Layouts in Playlists.

4. Turn off Launchpad player selection AND do not Tag the Launchpad. When users publish, they can give the template a specific naming convention (ex: EU BULGARIA xxxxx) and Clever Playlists can pull in said Launchpads based on the naming convention of the content. Example and  https://kb.korbyt.com/article/configuring-clever-playlists/
   

Desired end result: Give Launchpads a way of targeting Clever Playlists directly. Either via a manual selection of the existing accessible Clever Playlists, or by letting users assign Tags to the Launchpad, during the publishing process.