Deleted files and restore
Deletes in Sliick Files are strict: when a user removes a file’s last record attachment, Sliick deletes the bytes from the storage provider first, and only then removes it from the record. If the storage delete fails, the user sees an error and nothing changes. The record and the storage folder therefore always agree.
Where the bytes go
Section titled “Where the bytes go”| Provider | Where a deleted file lands |
|---|---|
| SharePoint | The site’s own recycle bin |
| Amazon S3, Google Cloud Storage, Azure Blob Storage | An object delete, recoverable where the bucket has versioning or soft delete enabled |
| Sliick Cloud Storage | Deleted permanently, never restorable |
Turn on your provider’s own recovery setting. Bucket versioning on Amazon S3 and S3-compatible providers, Object Versioning on Google Cloud Storage, and soft delete for blobs on Azure Blob Storage are what make Restore work at all. With them off, deletes are permanent and Restore reports the file as gone.
The Deleted Files tab
Section titled “The Deleted Files tab”Sliick Files Setup → Deleted Files lists the active provider’s deleted files for 100 days. Entries belonging to other providers are hidden until you switch the connection back, and a footer tells you how many there are. You can search by name and scroll through thousands of entries.
Each entry offers:
- Restore brings the bytes back through the provider’s own recovery and re-attaches the file to its original record, with tags and version history intact. It only succeeds inside the provider’s own retention window: SharePoint’s recycle bin is about 93 days, and Google Cloud Storage and Amazon S3 need bucket versioning to have been on when the file was deleted. A clear message tells you when a file is no longer recoverable and why.
- Remove entry and Clear list drop the retention entries themselves. This is metadata only, because the bytes were already deleted at delete time.
SharePoint restores in SharePoint
Section titled “SharePoint restores in SharePoint”There is no in-tab restore for SharePoint. The per-file action opens SharePoint’s own site recycle bin, where you, or the person who deleted the file, restore it. The restored file re-attaches to its record automatically the next time the record is viewed or synced. This is the same in both Service Principal and per-user (Delegated) modes.