This release opens the Winter '27 cycle with the biggest set of new capabilities File Slayer has shipped, putting real storage control in admins' hands: a rebuilt File Slayer Library with bulk deletion, a new Files component for record pages, and Hide Mode — a reversible alternative to deleting files outright.

 

The File Slayer Library, now with Purge

The Hit List Manager has been retired and replaced by the File Slayer Library — a modern interface for finding and managing files across your org, with full Slaybot integration.

 

Built into the Library, Purge lets admins define portable, criteria-based rules to find and permanently remove files across the entire org:

• Object-based criteria target files linked to records meeting specific conditions.
• All Files criteria search the entire org using date-based filters.
• Additional filters narrow by file size, name, extension, whether a file is blocked, and whether to include or exclude Asset and Library files.

 

The new Files component

A record page component for working with files everywhere in Salesforce, with faster Slaybot processing and an overhauled permission model. Favoriting, flexible table and tile views, and a new file viewer with built-in text extraction give users more control over how files are organized and reviewed without leaving the record page. Zip Files can also be directly extracted from records.

 

Hide Mode

A reversible approach to file management: instead of deleting unwanted files outright, Hide Mode removes them from your team's workspace while preserving them in the background for later review or removal.

 

Action Items:

1. Review and configure your Mode setting — File Slayer now supports two operational modes: "Hide files from view to delete later (Recommended)" and "Delete files immediately." Navigate to File Slayer Setup and confirm which mode is appropriate for your org. New installs default to Hide Mode. (v5.0)
2. Assign the Files (File Slayer) component permission set to licensed users — A new permission set, File Slayer Files Component, must be assigned to users who need access to the Files (File Slayer) record page component. Unlicensed users can view the Files (File Slayer) record-page component and benefit from hover previews and a file type column. Click here for more information. (v5.0)
3. Attachment support has been retired — File Slayer now works exclusively with the modern Salesforce Files framework. Attachments will no longer be processed by File Slayer, including the retroactive removal feature. Admins who configure File Slayer should ensure that orgs use Files exclusively before upgrading. (v5.16)
4. The Hit List Manager has been retired — The Hit List Manager has been replaced by the File Slayer Library, which covers the same file-finding and management work alongside Purge and full Slaybot integration. Update any bookmarks, saved links, or internal documentation pointing to the Hit List Manager, and confirm your users have the permission sets below so they can reach the Library. (v5.??)
5. Assign new permission sets for the File Slayer Library — Two new permission sets are now available: File Slayer Library (grants access to the Library and the Files component; requires a package license) and File Slayer Library Bypass (bypasses file security within the Library). The legacy "File Slayer End User" permission set is deprecated and should no longer be assigned to users. Review and assign the permission sets as appropriate for your team. (v5.17)

UI/UX

The File Slayer Library keeps getting easier to navigate. File size filters now offer a unit dropdown (KB, MB, or GB) instead of requiring a single scale, and a min/max range can also be set. The Blocked List tab now supports keyword and extension search, and gained a detail side panel showing more information about each blocked file. Additionally, the Library now uses the org's brand color, fully supports dark mode, and a Type column allows for clearer file identification.

 

The Purge tab footer now displays the name and saved status of your active filter, with a tooltip summarizing its criteria, and new icons in the Linked Records column show what objects they’re from. On narrow screens, the Linked Records column hides those icons to reduce clutter.

 

The File Slayer Setup tab now surfaces a clear, actionable error toast when a user without the "Customize Application" system permission attempts to open it. Rather than rendering a blank page or failing silently, Setup immediately identifies the missing permission and links directly to Salesforce documentation.

 

The Files component now sorts files by Created Date by default instead of Last Modified Date. Favoriting a file updates its record, keeping the list from reordering every time someone favorites a file.

 

Automation & Reliability

Slaybot processing speed has been significantly improved. Hardcoded delays and the halt functionality have been removed, and image evaluation now runs in parallel rather than serially. The practical result is a much faster time from component load to Slaybot completing its run.

Object search in the setup wizard is now substantially faster. The underlying logic was updated to identify configurable objects via the ContentDocumentLink's LinkedEntityId field, a direct, targeted approach that avoids the slow child relationship describes that previously caused long load times in complex orgs.

When files are blocked manually via the Library, the Files component, or through Slaybot, the retroactive removal batch job is now correctly triggered, ensuring that existing instances of those blocked files across the org are cleaned up automatically when the setting is enabled.

The deduplication process in both the File Library and the legacy record page component now re-links associated records from deleted duplicate files back to the original file, matching the behavior of the "Delete Duplicate Files on Individual Records" setting. If any error occurs during remapping, the entire deduplication operation rolls back safely to prevent data loss.

 

Security & Access

The packaged permission model has been overhauled. All existing permission sets have been updated, and two new sets have been introduced: File Slayer Library and File Slayer Library Bypass, for precise control over Library access and file security bypass behavior. The legacy "File Slayer End User" permission set is deprecated. A warning now appears in the setup wizard when "Email Message" is configured without the security bypass enabled, preventing a common misconfiguration. The "Default File Size" setting for the Library has been removed and is now hardcoded at 100KB.

 

For Purge, the Delete, Delete Selected, and Delete All actions are now disabled for orgs on a trial license, with a tooltip explaining that deletion is available in sandboxes and paid subscriptions.

 

Favoriting a file in the Files component now honors the "Bypass File Security: Files Component" setting.

“Delete All” Failed for File Slayer-Configured Objects in Object-Specific Searches — Clicking “Delete All” in the Purger during an object-specific search could incorrectly warn that no files could be deleted, even when the files were tied to objects configured for File Slayer. The flag identifying these files is now set correctly for object-specific searches. (v5.25)

 

JSON Heap Size Limit Error When Retrieving Files in the Library — Some orgs encountered a "System.LimitException: JSON string exceeds heap size limit" error when loading files in the File Library. File Slayer now detects this condition and automatically retries the request with a reduced batch size, preventing the failure from surfacing to users. (v5.23)

 

Date/DateTime "Is Blank" and "Is Not Blank" Filters Showed Unnecessary Input Field — When using the "Is Blank" or "Is Not Blank" operators on Date/DateTime filter fields in the Purge tab, an input field for a value was incorrectly displayed even though no value is required for those operators. The input field no longer appears for these operators. (v5.22)

 

XLSX Files Displayed a Broken Image Icon on Hover — Hovering over an XLSX file in the File Slayer Library showed a broken image with the text "Image Preview" instead of a file preview. XLSX files now display a proper hover preview. (v5.22)

 

Failed Image Previews Showed a Broken Image Instead of a Fallback — When an image in the Library preview popover failed to load, a broken image icon was displayed. The component now shows "No Preview Available" in place of the broken image. (v5.22)

 

"Invalid Sharing Type" and Email-Managed Link Errors During Deduplication — Deduplication in the File Library, the legacy component, and the "Remove Duplicate Files" automation failed when encountering User-based ContentDocumentLinks with sharing type "I," or when EmailMessage records had IsClientManaged set to false, causing the entire deduplication process to abort. The logic now automatically remaps restricted sharing types to Viewer and reroutes email-managed links to their parent or related records, allowing cleanup operations to complete without interruption. (v5.20)

 

"No such column 'ExternalDataSourceId'" Error Prevented Component Load — Users without access to the ExternalDataSourceId field on ContentVersion received a System.QueryException that caused the Files (File Slayer) component to fail to load entirely. The query has been updated to use the universally accessible ExternalDocumentInfo1 field to determine whether a file is external. (v5.20)

 

Infinite Spinner When Searching Objects in File Slayer Setup — When certain Salesforce objects (such as PersonalOrgInfo) were present in an org, searching for objects to configure in File Slayer Setup resulted in an infinite loading spinner triggered by an internal Salesforce error during child relationship describes. The search now uses the ContentDocumentLink's LinkedEntityId field to identify compatible objects, bypassing the problematic describe calls entirely. (v5.19)

 

File Library UI Broken When Lightning Web Security Was Disabled — In orgs with Lightning Web Security disabled, certain File Library components failed to render correctly due to namespacing and state-management issues. These have been resolved to ensure consistent behavior regardless of the org's LWS configuration. (v5.18)

 

Duplicate ContentDocumentLinks Created When Cloning Cases — When cloning a case that included emails while "Remove Duplicate Files" was enabled, redundant ContentDocumentLink records could be generated on the newly cloned emails if files appeared across multiple original emails. The cloning logic now ensures each unique file is linked to the new case exactly once. (v5.17)

 

New Salesforce Standard Objects Caused Errors in Setup Object List — Newly introduced Salesforce standard objects caused internal Salesforce errors when File Slayer attempted to retrieve their child relationships during setup object list construction, preventing the list from loading. Affected object types are now excluded from the describe operation. (v5.15)

 

Extension-Less Files Caused the Files Component to Fail to Load — If any file without a file extension was attached to a record, the Files (File Slayer) component would fail to load entirely, preventing access to all files on that record. The component now handles extension-less files gracefully. (v5.14)

 

Recursive Trigger Caused CPU Time Limit Errors During Link Remapping — When file link remapping operations triggered the ContentDocumentLink trigger recursively, the resulting loop produced "Apex CPU time limit exceeded" errors and timeouts. The trigger is now bypassed during remapping operations to eliminate the recursion. (v5.13)

 

Slaybot Incorrectly Moved Files to Recovery List on Deletion Failure — In the legacy File Slayer component, when Slaybot failed to delete a file, that file would disappear from the active list and appear in the Recovery section despite not being deleted. On page refresh, it would reappear, and the cycle would repeat. Error handling has been corrected, so files remain in their accurate state when Slaybot is unable to process them. (v5.13)

 

Slaybot Did Not Respect "File Security" Setting When Marking Keep — When Slaybot marked a file to be kept, the "File Security" bypass setting was not applied. Additionally, a single file failure would cause all remaining files in the same batch to be blocked as well. Slaybot now correctly respects File Security when marking files, and individual failures no longer prevent the rest of the batch from being processed. (v5.13)

 

"Slay Requires Licensed Owners" Setting Always Enforced — The File Library and Files component enforced the "Slay Requires Licensed Owners" feature parameter even when it was disabled, preventing users from processing files in configurations where the restriction should not have applied. The setting is now correctly respected. (v5.13)