It would reduce clutter and confusion for those searching through story maps if we could keep private the supporting maps behind public-facing story map applications. As it is, if someone looks for a particular story map, search results will turn up both the application made for the public and the map it is based on.
This becomes particularly unnecessary when there are layers of embedding. To use a personal example, this series of story maps (starting here: http://bit.ly/CCR15statewidemap) has 23 pieces (maps and applications), of which a good chunk only exist to make the story work. When all the supporting pieces have to be made public and searchable for any of it to work, it only makes it difficult for users to find what is actually relevant.
This previously posted idea mentioned the Shortlist application as an example. While a comment mentioned that the idea has been implemented, I could only find that it was implemented for that particular application example. It would be helpful if this was an option when making any type of story map application!