Events

Events are operational event records produced when key activities occur on your Files.com site, including Sync runs, Automation runs, Expectation evaluations, and other supported operations. For the full list of supported event types, see Event Types on the Subscriptions page.

The Events table shows all event records on your site, regardless of whether any subscription matched them. Event records are read-only and exist independently of any subscription or delivery. To check whether an event was delivered as expected, see Delivery Attempts.

Site Administrators see events across all workspaces. Workspace Administrators see only events from their own workspace.

Each event is associated with a workspace based on what produced it. File activity events use the workspace containing the recorded file path.

Sync, Automation, and Expectation events use the workspace of the Sync, Automation, or Expectation that ran. Client log events use the workspace of the user who generated the log, or the Default Workspace if that user has no workspace assignment. SSO and SIEM events are site-level and always appear in the Default Workspace.

Event records are retained for 30 days from creation. When an event is removed, its associated delivery attempts and email batch items are also removed. Completed folder delivery records are retained for 30 days after their last update; their removal does not delete files already delivered to the target folder. Log and Record Retention describes these lifetimes.

File Activity Events

File activity events let you route uploads, updates, downloads, deletions, moves, copies, and archival through Event Channels alongside operational outcomes. Each record describes a file operation and its recorded path. Folder operations do not produce these events.

File activity uses the Site and path recorded in History. For Partner Channel routes, native upload and copy arrivals and buffered mount uploads use the target path, while operations such as reads use the Channel path. Subscription filters must match the recorded action and path; selecting a Channel path does not redirect target-path arrivals into that scope.

Remote Server Mounts use their mount paths, and _/Sites/ views and Files.com Remote Server connections use each Site's own paths. Each Site controls its own event production and subscriptions.

Workflow run events remain on the Site that owns the workflow. Access Across Sites and Storage explains the relationship.

File activity event production is off by default. A Site Administrator enables File Activity Events on the Settings tab of Event Channels. Enabling the setting requires confirmation and creates records across all Workspaces, independently of whether a subscription matches them.

Review existing subscriptions before enabling the setting. Subscriptions with no event types selected match all event types, so they also begin matching file activity events. This can substantially increase delivery volume. Select specific event types or narrow the filters when a destination does not need that activity.

Selecting File Activity in a subscription does not turn production on. Subscriptions still select which event types and filters match, and both the subscription and target must allow the event's Workspace before it can be delivered. Enabling production across the site does not broaden those delivery boundaries. Folder Notifications operate separately and do not require this setting.

Details Recorded in Events

Each event record includes the following details.