Restore

The Restore feature allows Site Administrators to restore deleted files and folders through a self service process. It also allows Site Administrators to restore deleted users. Restore enables administrators to reverse deletions caused by mistakes, changing requirements, or automated actions without engaging the Files.com support team.

When to Use Restore

Use Restore when files or folders are deleted but are still required for active workflows, verification, reconciliation, or historical reference, especially when their absence blocks ongoing work or downstream processes. It is also appropriate when users are removed during role changes, off-boarding, or cleanups, and those users need to be reinstated to resume access or ownership of resources without manual re-creation.

Restore is commonly used when deletions occur unintentionally, when bulk operations or automation remove content or users unexpectedly, or when legal, regulatory, or audit requirements require timely access to previously deleted data or accounts.

Common Use Cases

Restore is typically used in the following scenarios to recover deleted files, folders, or users and minimize operational impact.

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 may also reenable access that no longer aligns with 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. In some cases, restore may be needed when off-boarding policies, expiration rules, or automated processes disable or delete users sooner than expected.

If restore is required frequently, it may 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.