Introduction

Managing files efficiently is essential for keeping a Salesforce org clean, compliant, and easy to use. In many orgs, teams collaborate heavily on documents, drafts, and shared files. However, until now, only file owners or Salesforce administrators could delete files, often creating unnecessary bottlenecks.

With the Spring ’26 preview release, Salesforce introduces a new system permission called Delete Salesforce Files. This permission allows more trusted users to delete files they can already view, streamlining file cleanup while preserving access control.

What’s New in Spring ’26?

Salesforce introduces a new user permission:

● Delete Salesforce Files

When this permission is assigned:

● Users can delete files they have access to view
● File cleanup no longer depends solely on file owners
● Admins are no longer required for routine file deletion

This enhancement was delivered based on customer feedback from IdeaExchange.

Why This Feature Matters

Before Spring ’26:

● Only file owners or admins could delete files
● Shared and outdated files accumulated quickly
● Admins handled frequent cleanup requests

With this enhancement:

● File cleanup happens faster
● Admin workload is reduced
● Collaboration improves across teams
● File governance remains permission-based

What Does the Permission Allow?

With Delete Salesforce Files permission:

● Users can delete any file they can view
● The permission applies across Salesforce Files
● Works in both Lightning Experience and Salesforce Classic

Users still cannot delete files they do not have access to.

Where This Feature Applies

This feature applies to:

● Salesforce Files
● Lightning Experience
● Salesforce Classic
● Standard UI-based file access

It is available across most Salesforce editions.

How to Enable Delete Salesforce Files

Option 1: Assign via Profile

● Go to Setup
● Open Profiles
● Select the target profile
● In System Permissions, enable Delete Salesforce Files
● Save

Option 2: Assign via Permission Set (Recommended)

● Go to Setup
● Open Permission Sets
● Create or open a permission set
● Enable Delete Salesforce Files
● Assign the permission set to selected users

Once assigned, users can delete files they are allowed to view.

Example Use Case

A project team collaborates on shared documents:

● Multiple users upload and revise files
● Old drafts and unused files accumulate
● The original file owner is unavailable

With the new permission:

● A trusted team member deletes outdated files
● Storage stays clean
● No admin involvement is required

Best Practices

● Assign this permission only to trusted users
● Use permission sets instead of profiles for flexibility
● Grant access to team leads or operations roles
● Combine with existing file sharing controls
● Review file deletion activity periodically

Security and Governance Considerations

● File deletion is permanent
● Users should understand the responsibility
● Avoid assigning this permission broadly
● Align usage with data governance policies

Limitations and Notes

● Feature is in preview
● Governed by Salesforce preview and beta terms
● Behavior may change before GA
● GA timeline is not guaranteed

Who Benefits the Most?

● Salesforce Administrators
● Operations and support teams
● Project managers
● Collaborative business teams
● Orgs with high file volumes

Conclusion

The Delete Salesforce Files permission introduced in Salesforce Spring ’26 is a practical improvement to file governance. By allowing trusted users to delete files they already have access to, Salesforce reduces admin bottlenecks while maintaining strong security controls.

For orgs dealing with file sprawl and frequent cleanup requests, this preview feature delivers meaningful productivity gains when enabled thoughtfully.

Blogs

Allow More Users to Delete Files Permission