Configure

Data retention🔗

FileRun removes some data by itself, on a schedule, and keeps the rest until somebody removes it. This page lists both, so that you know what your installation keeps, and for how long.

Everything FileRun removes by itself is removed by the scheduled tasks, so it happens only when the cron commands run on your server. See Command line tools. While maintenance mode is on, the scheduled tasks do nothing.

User accounts🔗

Users → Settings → Retention, fieldset User account retention policy. Both settings are 0 in a new installation, which turns them off.

• Deactivate inactive user accounts after deactivates an account that has not been used for that number of days.
• Delete inactive user accounts after deletes an account that is deactivated and has not been used for that number of days.

Caution

"Used" means opening the web interface. FileRun records the last time an account opened the web interface, and nothing else. An account that works only through WebDAV, the desktop sync app or the mobile apps looks unused, so these settings deactivate it, and later delete it, although it is in daily use.

Both numbers count from that last visit, or from the day the account was created if it never signed in. This has three consequences:

• An account you deactivated yourself is deleted as well, once it has been unused for that number of days.
• An account that signed up and is still waiting for your activation is deleted too, counted from the day it signed up. See User sign-up.
• When the second number is the same as the first, or smaller, an account is deleted on the same day it is deactivated.

Deleting an account does not delete its home folder. What it does remove is described under Deleting a user. The superuser, the guest accounts and FileRun's own system accounts are not affected by these two settings.

An account can also have its own expiration date, set when editing it. Once that date has passed, the daily task deactivates the account.

Guest accounts🔗

A guest account is deleted when nothing is shared with it any more, and after 30 days without use, unless you changed that number. See When guest accounts are deleted.

The user activity log🔗

Number of days to keep the user activity log entries, under Users → Activity logs → Settings. The default is 7.

Older entries are not deleted. The daily task moves them to the archive, under Users → Activity logs → Archive, where they stay until you delete them with Delete archive. On the activity log itself, Archive log moves every current entry to the archive at once.

Setting the number to 0 keeps every entry in the main log.

Nothing empties the archive by itself. On a busy installation it keeps growing until somebody deletes it.

The file activity log🔗

Kept for Number of days to keep the file activity log entries, 7 days by default, and then deleted. See File-based activity logs.

The e-mail log🔗

The messages FileRun sent are listed under E-mail → Logs for 2 days. No control panel setting changes that; the number of days is $config['system']['email']['logging']['retention_days'], see Advanced configuration. Older entries are removed each time a new message is sent.

Deleted files🔗

Items in the trash stay there until somebody empties it. FileRun empties the trash by itself only when the empty_trash.php command is scheduled, with the number of days you choose. See The trash.

Previous versions of files🔗

Kept by number, not by age: FileRun keeps at most Number of old versions to keep for each file old versions of each file, 2 by default. See File settings.

Shared links🔗

A shared link with an expiry date stops working when the date passes, and visitors see "This share is no longer accessible!". The link itself is not deleted: it stays listed under Files → Shared links in the control panel until somebody removes it.

Moving an item to the trash deletes the shared links created for it.

Sessions and app passwords🔗

• A browser session ends after the inactivity timeout, when one is set, and in any case six months after the sign-in. See Sign-in and passwords.
• An app password expires two years after it was created, and is then deleted. See App passwords.

What FileRun never deletes by itself🔗

• The files in the users' folders, apart from the trash as described above. To remove old files on a schedule, see Deleting old user files.
• The archive of the user activity log.
• Regular user accounts, unless you set the retention days above.