This presentation examines:
* Sharing links and the difference between links and file paths
* Managing (and revoking) content sharing
* Limitations in library and list permissions
2. OFFICIAL
• A file path to a file or folder is different from a link or a sharing link
• Links are persistent…renaming a file or folder changes the file path
• Links and sharing links are security aware…
• …and shared links can be revoked
• While you can manage individual documents easily (-ish), there is no
easy way to bulk manage sharing links…
• …but, you can write reports and execute actions using CSOM
PowerShell script, which is a basic SharePoint developer skill
Key Points
4. OFFICIAL
• Let’s have a look at the format of a content link and what those funny
URL codes mean
https://microz.sharepoint.com/:f:/r/sites/PowerMarkDemo/Projects/Ad
min%20Training?csf=1&web=1&e=8ElpXD
• csf=1 means sharing with people with existing access – legacy code!
• e=8ElpXD (or d=) is a unique hash code which ensures a link
continues to work if a file is moved
Key Points
5. OFFICIAL
• Best practice is to avoid default item level permissions, and in particular
change link defaults to read-only from edit rights…refer to Manage
sharing settings for SharePoint and OneDrive in Microsoft 365
• The sharing settings page also explains different security levels and
turning on/off external file sharing
• See next page to understand the meaning of URL link format
• Beware…after your library reaches 100,000 items, item level permissions
only are permitted
• There is a limit of 50,000 unique permissions (known as security scopes),
but performance can degrade after 5,000 unique permissions…refer to
StackExchange for a further discussion
Key Points
6. OFFICIAL
simon@powermark.net.au
+61 430 986 682
LinkedIn: https://www.linkedin.com/in/simonrawson/
Contact me for questions or professional
guidance on M365 strategies, solution &
information architecture, training, information
and knowledge management