File Slayer uses a combination of seat licenses and permission sets to control who can see the record page component and who can use its advanced "cleanup" features.

 

Licenses are required for:

• Users who own or use object records (such as Case, Account, Email Messages) enabled for File Slayer and will be performing file cleanup on individual records through the Files (File Slayer) Component
• System Admins who configure the app or do org-wide file cleanup through the File Slayer Library
• The Automated Case user (standard Email-to-Case) or the Email to Case Premium context user.

For example, in a typical service organization, File Slayer would be enabled for the Case and Email Message objects. If you have 90 agents working cases and doing file cleanup, 8 support managers doing org-wide file cleanup, the Automated Case user (or the E2CP context user), and the System Administrator configuring File Slayer, you would need a total of 100 licenses. All other users in the org can still benefit from our record page component, but would only need to be assigned the "File Slayer Files Component" permission set.

 

Licenses are not needed for:

• Users who own or use object records not enabled for File Slayer.
• Inactive users.
• Community, Portal, Self-Service, or Guest users.
• Queues.

 

Unlicensed users working on records for objects enabled for File Slayer will see the following message on the component. These users will be able to see all files, use the hover previews, and sort by "Type," but will not be able to block files or switch to the Clean View. 

 

In the File Slayer Library, files related to records owned by unlicensed users will not be eligible for blocking:

 

File Slayer’s Retroactive Removal feature only looks at files related to records owned by licensed users. Files inserted by an unlicensed integration or context user will not be checked against the File Slayer Block List and will not be automatically flagged for removal.