Restore
The Restore feature lets Site Administrators restore deleted files and folders and restore deleted users through a self-service process. Restore lets administrators reverse deletions caused by mistakes, changing requirements, or automated actions without engaging Files.com Support.
When to Use Restore
Use Restore when files or folders are deleted but are still needed for active workflows, verification, reconciliation, or historical reference, especially when their absence blocks ongoing work. Use it for users when someone was removed during a role change, off-boarding, or a cleanup and needs to be reinstated to resume access or ownership of resources without manual re-creation.
Restore is also the right tool when deletions occur unintentionally, when bulk operations or automation remove content or users unexpectedly, or when legal, regulatory, or audit work calls for timely access to previously deleted data or accounts.
Common Use Cases
Operational Recovery
Recover files and folders deleted by mistake or during bulk operations, automation, or cleanup tasks. Restore eliminates the need to rebuild folder structures, re-upload large volumes of data, or rely on Support for recovery.
User Reinstatement
Reinstate users who were deleted during transitions, reorganizations, or off-boarding, without recreating accounts or reconfiguring permissions.
Legal, Compliance, and Audits
Restore deleted files or users to support audits, investigations, legal inquiries, or compliance reviews when retention or access requirements change.
Automation and Integration Rollbacks
Reverse unintended deletions caused by scripts, integrations, or automated workflows by restoring affected files, folders, or users.
Things to Consider Before Restoring
Use Restore thoughtfully. Bulk restores can reintroduce outdated or unnecessary files and users, and restoring users can re-enable access that no longer matches current roles or policies. Review restore selections and verify permissions and ownership after restoration.
Restore is a recovery step within user and content lifecycle management, not a replacement for well-defined onboarding, off-boarding, or deletion processes. Restore is sometimes needed when off-boarding policies, expiration rules, or automated processes disable or delete users sooner than expected.
Frequent need for Restore can indicate issues in onboarding, off-boarding, access permissions, bulk operations, or automation. Treat repeated restores as a signal to review how deletions are performed and validated, rather than relying on Restore as a routine recovery step.