Forum Discussion
Transition from FTP to SharePoint Online
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.
- Jennifer RideoutDec 12, 2018Brass Contributor
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?
- Dec 12, 2018Could 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.- Jennifer RideoutDec 12, 2018Brass Contributor
The site collection permissions are exactly what is driving it - specific to anonymous links. We don't allow them in our tenant without an expiry, and we have business cases that need it, thus this approach.
This site collection would be the only one to allow Anyone links, but we wouldn't want to give the user the ability to share from any other document library than the one they requested. Aside from setting up a site for each user or project, this seemed like a good option.
Thank you so much for your thoughts! I'm going to continue to explore it more to see what the best options are, but this might address our business case and not overwhelm our tenant with user specific site collections.