we have workbooks, from within which users will kick off pipeline analysis jobs. the workbook serves 2 purposes:

1. sort of a 'silo' from which to contain multiple analysis jobs. the outcome of these jobs will all get dropped in this workbook. this gives users a way to historically see what files went with what. Without workbooks the parent folder would accumulate lots of misc analysis jobs and becocme unmanageable

2. we want to let users deposit whatever misc non-pipeline related files they have. these could be anything.

The question is:

For all the user really cares, the pipeline webpart is the same thing as the files webpart. they store in different places, but they will not really know or care about this subtlety. is there any downside to simply using the pipeline folder for points 1 and 2? other than possible name conflicts or something?

putting non-pipeline related files in a separate files webpart is technically preferable, but I dont know how to make the end-user experience of that work. they'd end up depositing all the files they want to use in the pipeline in the files webpart and get confused as to why they couldnt start the pipeline.

i'd appreciate any suggestions or thoughts. thanks.