Organization Scoped Sharing Link, Discover and Check Permissions

%3CLINGO-SUB%20id%3D%22lingo-sub-874607%22%20slang%3D%22en-US%22%3EOrganization%20Scoped%20Sharing%20Link%2C%20Discover%20and%20Check%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-874607%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20had%20a%20few%20cases%20of%20users%20reporting%20that%20they%20can%20see%20documents%20that%20they%20shouldn't%20see%20via%20the%20%22Discover%22%20section%20of%20Outlook%20mobile%2C%20OneDrive%20and%20Delve.%20In%20investigating%20these%20cases%2C%20it%20appears%20that%20%22organization%22%20scoped%20sharing%20links%20were%20created%20for%20the%20files%20or%20folders%20in%20which%20the%20files%20reside.%20I'm%20trying%20to%20determine%20the%20consequences%20of%20creating%20such%20a%20link%20for%20a%20file%20or%20folder%20(ie%3A%20should%20they%20show%20up%20to%20folks%20via%20%22discover%22%20and%20is%20there%20any%20way%20to%20control%20that%3F).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet's%20say%20a%20user%20selects%20a%20file%20or%20folder%20in%20a%20SharePoint%20Library%20and%20clicks%20the%20Share%20button.%20They%20click%20the%20audience%20selector%20and%20choose%20%22People%20in%20%3CTENANT%3E%20with%20the%20link%22%2C%20leave%20the%20%22Allow%20editing%22%20box%20checked%20and%20proceed%20to%20specify%20one%20or%20more%20people%20to%20whom%20the%20link%20will%20be%20sent.%26nbsp%3B%3C%2FTENANT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EObviously%2C%20those%20people%20that%20were%20specified%20will%20get%20the%20email%20with%20the%20link.%20Because%20of%20how%20the%20link%20is%20scoped%2C%20everyone%20in%20the%20tenant%26nbsp%3B%3CEM%3Etechnically%3C%2FEM%3E%20has%20edit%20permissions%20to%20the%20file%2Ffolder%2C%20but%20they%20don't%20have%20the%20link.%20In%20this%20sense%2C%20it%20was%20my%20understanding%20that%20these%20links%20were%20like%20%22unlisted%22%20videos%20on%20YouTube.%20That%20is%2C%20without%20the%20link%20to%20get%20to%20that%20video%2C%20people%20can't%20find%20it%3B%20it%20doesn't%20show%20up%20in%20search%20results%2C%20isn't%20indexed%20by%20Google%2C%20etc.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20the%20reports%20of%20documents%20showing%20up%20in%20discover%20seems%20to%20indicate%20that%20something%20(MS%20Graph%3F)%20is%20actively%20displaying%20the%20files%20to%20users%20who%20have%20not%20specifically%20been%20sent%20the%20link.%20I%20understand%20this%20is%20really%20a%20%22security%20by%20obscurity%22%20thing%20and%20that%20those%20users%26nbsp%3B%3CEM%3Etechnically%3C%2FEM%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3Edo%20have%20permissions%20to%20the%20files%20via%20that%20link.%20Although%2C%20this%20last%20part%20brings%20up%20another%20interesting%20point.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBeing%20all%20too%20familiar%20with%20SharePoint%20permissions%2C%20I%20always%20reach%20for%20the%20%22Check%20Permissions%22%20tool%20(in%20Advanced%20Permissions)%20to%20determine%20what%20access%20a%20specific%20user%20has%20to%20a%20file%2C%20folder%2C%20item%20or%20site.%20The%20problem%20is%20that%20that%20tool%20does%20not%20factor%20in%20those%20%22sharing%22%20links.%20Specifically%2C%20when%20I%20did%20%22Check%20permissions%22%20on%20the%20document%20the%20user%20was%20accessing%2C%20the%20result%20was%20%22None%22.%20So%2C%20in%20my%20experience%2C%20user%26nbsp%3B%3CEM%3Edoes%20not%3C%2FEM%3E%20have%20permission%20to%20view%20the%20file.%20Except%20they%20do%2C%20via%20that%20sharing%20link.%20So%2C%20the%20Check%20permissions%20tool%20either%20needs%20to%20be%20update%20to%20account%20for%20sharing%20links%2C%20or%20we%20need%20another%20method%20of%20enumerating%20actual%20user%20permissions%20to%20the%20object.%20Maybe%20there%20is%20such%20a%20tool%20in%20the%20O365%20admin%20center%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-874607%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPermissions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESites%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-882982%22%20slang%3D%22en-US%22%3ERe%3A%20Organization%20Scoped%20Sharing%20Link%2C%20Discover%20and%20Check%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-882982%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F86417%22%20target%3D%22_blank%22%3E%40null%20null%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20initial%20impression%20is%20correct.%20While%20the%20link%20does%20work%20for%20anyone%20in%20the%20organization%2C%20it%20doesn't%20actually%20grant%20access%20to%20any%20user%20until%20they%20have%20either%20been%20sent%20the%20link%20(e.g.%20the%20send%20link%20option%20in%20the%20share%20dialog)%20or%20they%20click%20on%20it.%20If%20you%20create%20a%20link%20but%20don't%20send%20it%20to%20anyone%2C%20no%20one%20should%20be%20able%20to%20find%20it%20in%20Discover%20or%20Shared%20With%20Me.%20Hope%20that%20helps!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3ESenior%20Program%20Manager%2C%20OneDrive%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-883193%22%20slang%3D%22en-US%22%3ERe%3A%20Organization%20Scoped%20Sharing%20Link%2C%20Discover%20and%20Check%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-883193%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%2C%20that%20does%20help%20a%20bit.%20I'm%20still%20puzzled%20by%20the%20%22Discover%22%20feature%2C%20though.%20It%20seems%20like%20it%20would%20be%20useful%20in%20a%20smaller%20and%20more%20peer-based%20organization%2C%20where%20it's%20easier%20to%20keep%20the%20%22sensitive%20documents%22%20under%20tighter%20control.%20However%2C%20in%20an%20academic%20environment%20with%20~40%2C000%20users%2C%20about%20~5%2C000%20of%20which%20(faculty%20and%20staff)%20have%20their%20own%20definition%20of%20%22sensitive%22%2C%20it%20seems%20like%20it's%20a%20big%20problem%20just%20waiting%20to%20happen.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere's%20no%20clear%20documentation%20(that%20I've%20found%2C%20anyway)%20as%20to%20what%20shows%20up%20in%20Discover%20and%20how.%20It's%20all%20based%20on%20MS%2FOffice%20Graph%2C%20but%20what%20does%20that%20really%20mean%20in%20practical%20terms.%20In%20this%20particular%20example%2C%20let's%20say%20that%20org-scoped%20sharing%20link%20was%20created%20and%20sent%20to%20one%20employee.%20That%20employee%20happens%20to%20be%20in%20regular%20correspondence%20with%20a%20particular%20student.%20The%20employee%20gets%20the%20email%20and%20opens%20the%20document.%20Does%20Graph%20see%20the%20situation%20and%20say%20(in%20simplified%20terms%2C%20obviously)%3A%20%22that%20student%20is%20conversing%20with%20that%20employee%20and%20that%20employee%20just%20opened%20a%20file%20that%20the%20student%20also%20has%20access%20to%20via%20that%20link...let's%20show%20that%20to%20the%20student%20since%20they%20may%20want%20to%20see%20it%2C%20too!%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20clarify%2C%20I'm%20taking%20the%20student%20at%20their%20word%20when%20they%20say%20%22I%20found%20the%20document%20in%20the%20Discover%20section%20of%20the%20Outlook%20app%22%20and%20trying%20to%20figure%20out%20how%20it%20ended%20up%20appearing%20there.%20I%20have%20not%20seen%20proof%20that%20the%20student%20saw%20it%20there%2C%20but%20I%20do%20have%20a%20record%20(from%20the%20audit%20log)%20that%20they%20accessed%20the%20file%2C%20so%20it's%20reasonable%20to%20assume%20they're%20being%20honest.%20What%20we%20don't%20seem%20to%20have%20is%20a%20way%20to%20determine%20to%20whom%20that%20org-scoped%20link%20was%20sent%20(except%20to%20ask%20the%20person%20who%20sent%20it).%20So%2C%20there%20are%20a%20few%20gaps%20in%20the%20audit%20trail%2C%20which%20makes%20it%20hard%20to%20know%20exactly%20what%20happened.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-883662%22%20slang%3D%22en-US%22%3ERe%3A%20Organization%20Scoped%20Sharing%20Link%2C%20Discover%20and%20Check%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-883662%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F86417%22%20target%3D%22_blank%22%3E%40null%20null%3C%2FA%3EI%20have%20this%20issue%20all%20the%20time%20with%20Delve%20and%20customers%20not%20liking%20that%20it%20highlights%20content%20that%20users%20may%20not%20necessarily%20know%20they%20have%20access%20to%2C%20and%20in%20some%20cases%20shouldn't%20have%20access.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20Delve%20is%20completely%20permission%20based%2C%20if%20a%20user%20does%20not%20have%20permission%20to%20the%20file%20they%20100%25%20will%20not%20see%20it.%20This%20is%20the%20basis%20that%20SharePoint%20is%20built%20on%20so%20we%20can%20be%20assured%20that%20this%20works.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20organisational%20wide%20links%20you%20can%20see%20which%20users%20have%20accessed%20the%20file%20by%20looking%20at%20the%20unique%20permissions%20on%20that%20file%2C%20whilst%20the%20link%20is%20created%20users%20do%20not%20have%20permissions%20to%20that%20file%20until%20they%20access%20the%20link%20and%20at%20that%20point%20they%20are%20added%20into%20the%20unique%20permissions%20on%20the%20file.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-883667%22%20slang%3D%22en-US%22%3ERe%3A%20Organization%20Scoped%20Sharing%20Link%2C%20Discover%20and%20Check%20Permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-883667%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F86417%22%20target%3D%22_blank%22%3E%40null%20null%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F214649%22%20target%3D%22_blank%22%3E%40Andrew%20Hodges%3C%2FA%3E%26nbsp%3Bis%20correct.%20I'd%20also%20check%20out%20this%20documentation%20for%20more%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdelve-for-office-365-admins%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Einfo%3C%2FA%3E%20on%20Delve.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20for%20your%20specific%20use%20case%2C%20in%20order%20for%20the%20student%20to%20have%20found%20the%20document%20in%20Discover%2C%20someone%20must%20have%20sent%20it%20to%20them%20(either%20via%20e-mail%20or%20some%20other%20client%20and%20then%20they%20clicked%20on%20it).%20Unfortunately%2C%20if%20you%20don't%20see%20an%20audit%20even%20for%20someone%20sending%20it%20to%20them%20directly%2C%20then%20it%20must%20have%20happened%20outside%20of%20where%20we%20(the%20service)%20can%20track%20it.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnother%20possibility%20is%20that%20the%20file%20is%20on%20a%20site%20that%20is%20accessible%20by%20the%20student%20(a%20site%20shared%20with%20the%20entire%20organization%20maybe%3F)%20and%20that%20could%20also%20cause%20things%20to%20show%20up%20there.%20Hope%20that%20helps%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3ESenior%20Program%20Manager%2C%20OneDrive%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

We've had a few cases of users reporting that they can see documents that they shouldn't see via the "Discover" section of Outlook mobile, OneDrive and Delve. In investigating these cases, it appears that "organization" scoped sharing links were created for the files or folders in which the files reside. I'm trying to determine the consequences of creating such a link for a file or folder (ie: should they show up to folks via "discover" and is there any way to control that?).

 

Let's say a user selects a file or folder in a SharePoint Library and clicks the Share button. They click the audience selector and choose "People in <tenant> with the link", leave the "Allow editing" box checked and proceed to specify one or more people to whom the link will be sent. 

 

Obviously, those people that were specified will get the email with the link. Because of how the link is scoped, everyone in the tenant technically has edit permissions to the file/folder, but they don't have the link. In this sense, it was my understanding that these links were like "unlisted" videos on YouTube. That is, without the link to get to that video, people can't find it; it doesn't show up in search results, isn't indexed by Google, etc. 

 

However, the reports of documents showing up in discover seems to indicate that something (MS Graph?) is actively displaying the files to users who have not specifically been sent the link. I understand this is really a "security by obscurity" thing and that those users technically do have permissions to the files via that link. Although, this last part brings up another interesting point. 

 

Being all too familiar with SharePoint permissions, I always reach for the "Check Permissions" tool (in Advanced Permissions) to determine what access a specific user has to a file, folder, item or site. The problem is that that tool does not factor in those "sharing" links. Specifically, when I did "Check permissions" on the document the user was accessing, the result was "None". So, in my experience, user does not have permission to view the file. Except they do, via that sharing link. So, the Check permissions tool either needs to be update to account for sharing links, or we need another method of enumerating actual user permissions to the object. Maybe there is such a tool in the O365 admin center?

 

 

4 Replies
Highlighted

Hi @ChadKealey,

 

Your initial impression is correct. While the link does work for anyone in the organization, it doesn't actually grant access to any user until they have either been sent the link (e.g. the send link option in the share dialog) or they click on it. If you create a link but don't send it to anyone, no one should be able to find it in Discover or Shared With Me. Hope that helps!

 

Stephen Rice

Senior Program Manager, OneDrive

Highlighted

Thanks, @Stephen Rice, that does help a bit. I'm still puzzled by the "Discover" feature, though. It seems like it would be useful in a smaller and more peer-based organization, where it's easier to keep the "sensitive documents" under tighter control. However, in an academic environment with ~40,000 users, about ~5,000 of which (faculty and staff) have their own definition of "sensitive", it seems like it's a big problem just waiting to happen. 

 

There's no clear documentation (that I've found, anyway) as to what shows up in Discover and how. It's all based on MS/Office Graph, but what does that really mean in practical terms. In this particular example, let's say that org-scoped sharing link was created and sent to one employee. That employee happens to be in regular correspondence with a particular student. The employee gets the email and opens the document. Does Graph see the situation and say (in simplified terms, obviously): "that student is conversing with that employee and that employee just opened a file that the student also has access to via that link...let's show that to the student since they may want to see it, too!"

 

To clarify, I'm taking the student at their word when they say "I found the document in the Discover section of the Outlook app" and trying to figure out how it ended up appearing there. I have not seen proof that the student saw it there, but I do have a record (from the audit log) that they accessed the file, so it's reasonable to assume they're being honest. What we don't seem to have is a way to determine to whom that org-scoped link was sent (except to ask the person who sent it). So, there are a few gaps in the audit trail, which makes it hard to know exactly what happened.

Highlighted

@ChadKealeyI have this issue all the time with Delve and customers not liking that it highlights content that users may not necessarily know they have access to, and in some cases shouldn't have access. 

 

However, Delve is completely permission based, if a user does not have permission to the file they 100% will not see it. This is the basis that SharePoint is built on so we can be assured that this works.

 

For organisational wide links you can see which users have accessed the file by looking at the unique permissions on that file, whilst the link is created users do not have permissions to that file until they access the link and at that point they are added into the unique permissions on the file. 

Highlighted

Hi @ChadKealey ,

 

@Andrew Hodges is correct. I'd also check out this documentation for more info on Delve.

 

As for your specific use case, in order for the student to have found the document in Discover, someone must have sent it to them (either via e-mail or some other client and then they clicked on it). Unfortunately, if you don't see an audit even for someone sending it to them directly, then it must have happened outside of where we (the service) can track it. 

 

Another possibility is that the file is on a site that is accessible by the student (a site shared with the entire organization maybe?) and that could also cause things to show up there. Hope that helps,

 

Stephen Rice

Senior Program Manager, OneDrive