Destination collabs unclear, possibly disruptive #24
Description
The wizard asks users that click a link to select a destination collab. A user can find a link to a BSP usecase pretty much anywhere, so the dummy-proof assumption should be that a user has absolutely no knowledge of the underlying technicalities or implications of this choice. It is entirely possible that a user just randomly clicks a collab they see in the list, to continue the process, and the import clutters and litters that collab with files.
It's better UX to suggest creating a new collab, specific for this usecase, and to keep the existing list of collabs underneath that, as a secondary option, but clarifying that the contents of the usecase will be merged/imported into it.
The choice of destination collab could also be remembered perhaps?