Forum Discussion
Transition from FTP to SharePoint Online
I'm looking for options to replace my company's existing FTP process. In most cases, it doesn't require the creation of an entire team site, but does require more than just a OneDrive folder. I'd like to consider the following approach:
- SharePoint online site collection (Communication template)
- Have user complete a form and upon submission, a document library is created with only permissions assigned to the requesting user and our site admins.
- User can create files and folders from within the document library and use the secure sharing experience to share files and folders.
Basically, just create a document library for a requesting user, and lock down permissions. Then, they can function within that library the same way they would in their OneDrive folder.
I haven't found any major limitations in the number of document libraries per site, and the scale-able storage to 25TB is plenty sufficient. Am I missing something, or does this seem like a sound approach?
Thanks in advance for your thoughts!
5 Replies
- The issue you're going to run into is assigning permissions. Are all the users already users that exist in your AD or random external users? If your working with external users the only thing that I know you can really automate is generating sharing links via Flow. Which this whole process can be done using. However, last I checked there was no way to generate Sharing links with the "specific users" option.
If you are ok with using generic "Anyone with the link" links to access theses folders for your endpoint / users then the method could be done fairly easily. But if you need to make sure they are secured it's going to add quiet a bit of complication to it.We have a third-party add in that allows us to create the library and reassign permissions - and that is only for our internal folks. When they want to share files with an external user, they would create the folder in their document library and share that folder using the Spec. Ppl. link option. This would enable them to have one document library that functions as the JSmith library, and within it, they can have whatever folders they'd like.
I'm just not sure if there are any other permissions or security items we should be thinking of by using document libraries over separate site collections. OneDrive is too personal, a team site is too much, is a site with libraries a good middle ground?
- Could be. Like you said the limits are pretty large. What you need to think about around that is supreme permissions via site collection admins. If only at any time a few people can see everything then it should work. With using sites you can get per site collection sharing option restrictions etc. So if you want to enable some to be able to use anonymous links and not others you can, if you do everything in one site your limited to one setting and that's it for all libraries.
Other than that, I can't really think of much more myself either for that scenario.
