Child Site History and Logging

File and folder actions on a Child Site can happen directly within that site or through the Parent Site's underscore folder. Actions through the Parent Site are recorded in both sites' History Logs, so central administrators and the people responsible for the Child Site can review what happens to its content.

The Parent Site's History uses the _/Sites/<child-site-id>/... path. The Child Site's History uses its own file or folder path. For example, a Parent Site upload of a new file to _/Sites/123/incoming/report.csv appears at that path on the Parent Site and at incoming/report.csv on Child Site 123. This applies to actions performed by Parent Site users and workflows, including Automations and Syncs.

Each site's configured notifications, webhooks, and Automations can respond to its own record when the action, path, and other conditions match. The same activity can trigger responses on both sites.

Configure each response on the site responsible for that work, using the path as it appears there. A Child Site Automation watching for new files in incoming can therefore respond to the Parent Site upload in the example above.

For copies and moves across site boundaries, each Child Site records its part of the transfer. A source Child Site records a file read and, for a move, deletion of the source.

A destination Child Site records creation of the file. A copy or move entirely within one Child Site retains the copy or move action there. Select trigger actions to match what is recorded on the site running the response.

Activity performed directly within a Child Site is recorded in that Child Site only and does not trigger Parent Site notifications, webhooks, or file-action Automations. This also applies when a Parent Site user with delegated access switches into the Child Site and works there.

Automation and Sync run logs are separate from file History. Each Automation or Sync belongs to the site where it is configured, and its run logs remain there.

A Parent Site workflow that changes Child Site files has its run logs on the Parent Site, while the file actions it produces through the underscore folder are recorded on both sites. Use the workflow's run logs to review its overall outcome and History to review the actions on the files.