ShareMaster V2 is in beta, a complete rebuild. See what is new and request access →
Features All features overview
Migration Tools Overview Structure and content OneDrive ↔ SharePoint Content only Structure only Move / Copy Upload from this computer Download to this computer Dropbox to SharePoint Resume and incremental runs
Recycling Bin Overview Browse a site's recycle bin Empty recycle bins in bulk Restore and purge history
Archive Overview Configure the tenant On Demand Archive Restore Archived Files Archive Savings Report Blob Viewer
Optimise Storage Tools Overview Delete all items in a list Delete all files and folders in a library Remove empty folders Remove duplicate files Reduce image sizes Delete sites and subsites
SharePoint Tools Overview Tenant Explorer SharePoint Explorer Easy Settings Fix renamed groups List Explorer Search the Preservation Hold Library
Replace Overview Replace in SharePoint Replace in local files Find password-protected files
Shared Links Overview Report shared links Report unique permissions Remove a person from sharing links Remove shared links Remove unique permissions
Version History Overview Version trimming Version trimming report Reset file version
Reports Overview Inventory report Folder inventory Site and subsite storage Security matrix Teams permissions Pre-migration analysis Compare items Dropbox to Microsoft 365 compare Duplicate file report Empty folder report Image size report Recycle bin report Unused licences Report history
V2 beta Pricing Demos Blog Guides Use cases Compare Tools Alerts FAQ Contact Sign in Start free trial
  1. Home
  2. Documentation
  3. Archive

What happens when someone clicks an archived file

The whole path, and who is allowed to do it

Someone in a document library sees a file with its usual name and clicks it. This is everything that happens between that click and the file opening, and every point at which the answer can be no.

Reads only. Nothing in SharePoint is changed.

What it tells you

  • Permissions are never bypassed. The file is fetched as the person who clicked, using their own SharePoint session, so someone who could not open the original cannot open the archived copy.
  • The placeholder itself contains no credential of any kind. It holds a pointer and nothing else, and both readers of it refuse outright if a credential-shaped value ever appears in one.
  • The link that fetches the bytes is short-lived and signed with a Microsoft identity, not with an account key.
  • A placeholder set to put the file back ends with the real file back in SharePoint, opening in Word or Excel as it always did. One set to download a copy ends with a download.

How it runs

  1. The click reaches your Archive application. Because setup step 3 registered .shurl with Microsoft as belonging to it. Or, before that has propagated, the person uses Open with ShareMaster in the library toolbar, where the Archive app is deployed.
  2. The request lands on your endpoint. In your own Azure subscription. It is told which item was clicked and by whom - and nothing else: the request carries no access to the file.
  3. The person signs in. With their own Microsoft account, the first time and whenever their sign-in has lapsed.
  4. The placeholder is read as that person. Their own permissions decide. If they cannot read the placeholder, this is where it stops.
  5. The file comes back. The placeholder says which: a short-lived, signed link downloads a copy, or the file is written back into SharePoint in place of the placeholder - same item, same history - and opened.

What it will not do

  • A file put back by a click keeps its Created date and Created By, but its Modified date becomes the time of the click and Modified By becomes the person who clicked. The click writes as that person, and SharePoint does not let it set those two. Restore Archived Files, run from ShareMaster, keeps all four.
  • A restored file no longer saves you space. If most people restore most files, the saving erodes - which is why a placeholder can be set to download a copy instead, for things nobody needs back in SharePoint.
  • A file in a folder someone syncs to their PC behaves differently, and that case is not yet covered.

See every feature