3 ms·
Aside from the annoyance factor, this is a huge gaping hole allowing information leaks. Let's replace `foo.jpg` with `Annual Review 2021.pdf`. You send employee
by vidanay 5y ago
Aside from the annoyance factor, this is a huge gaping hole allowing information leaks. Let's replace `foo.jpg` with `Annual Review 2021.pdf`. You send employee #1 their review, and then send employee #2 theirs, but forget about this quirk, and instead of keeping, you overwrite. Now employee #1 can open employee #2's confidential info in their link.
- lelandfe 5y agoThankfully (I guess?) that isn't a problem: the files are uploaded to Sharepoint folders specific to conversations or channels. So the issue I detailed would only rear it's head in your scenario if you sent employee #1 their review twice. Humorously, this issue does not occur when uploading files directly in the Sharepoint interface – despite the interface looking like it stepped out of Windows 95.
- vidanay 5y agoI'll have to verify this tomorrow, but I am 99% certain I have seen this message when sharing the same file name between different 1:1 conversations. I guess it's possible that it is a configuration issue since our Teams/SharePoint is self-hosted at my company.
- lelandfe 5y agoYeah, I am not a licensed Microsoft config guy whatsoever, but do know that Sharepoint can be configured to the moon and back. That was, after all, the reason my old org went with Teams over Slack. So it's not hard for me to imagine that it could be set up in a way that causes this issue across discussions. Yuck.