Configure

Activity log actions🔗

Every entry of the activity log names the action that was performed, such as Core.login or Drive.upload. This page lists these names, grouped by the application they belong to, and the configuration options that use them.

The name of an action🔗

The name of an action is the name of the application that performs it, a dot, and the action itself. Core performs the actions about user accounts, signing in and the control panel. Drive performs the actions on files and folders.

Important

FileRun 2026.4.0 added the application to the names. Earlier versions named the actions without it: login instead of Core.login, upload instead of Drive.upload. The update renames the entries of the activity log, of its archive and of the e-mail notification rules, but not your configuration. If customizables/config.php or the customizables/events folder names actions, change them to the new names. The two options of the e-mail notifications about files are the exception: they keep the names without the application, and moved to $config['Drive'] (see below).

Where the names are used🔗

• The CSV export of the activity log, in the Action key column.
• $config['Drive']['email_notification']['basic_actions'], the actions of Drive a user is e-mailed about when the account has e-mail notifications turned on. See Advanced configuration.
• $config['Drive']['email_notification']['folder_based']['limit_actions'], the actions of Drive that the per folder notifications leave out.
• $config['system']['custom_event_scripts'], the actions that run a custom event script. The script of an action is named after it, in the customizables/events folder: customizables/events/Drive.upload.php runs for Drive.upload.
• The activity log stream ($config['system']['activity_log_stream']). Each line has the application in its app field, and the action without the application in its action field.

For example, to e-mail the users only about the files uploaded and downloaded by others:

 1$config['Drive']['email_notification']['basic_actions'] = [
 2    'receive_upload',
 3    'receive_download'
 4];

Note

The options under $config['Drive'] are the options of that application, so they take the name of the action without the application: receive_upload, not Drive.receive_upload. So do the $config['app']['logging']['skip_receive_...'] options: skip_receive_download, not skip_receive_Drive.download.

Core🔗

Drive🔗

Actions on files and folders🔗

Entries for the other users🔗

When a user acts on a file or a folder, FileRun also writes an entry in the activity log of every other user whose home folder holds that file, so that they see what somebody else did to it. These entries are named after the action, with receive_ in front of it. Their label names the user who performed the action, which the lists of the control panel show as "Somebody". The advanced configuration page explains how to turn them off.