Child Sites History and Logging

File actions that impact a child site could happen within the parent site (through the underscore folder) or on the child site. To keep things simple, and to prevent multiple notification events being raised for a single action, each action is logged only in the site where the user or process is authenticated.

To decide whether to configure automated activities in the child site or in the underscore folder on a parent site, determine whether those activities need to trigger downstream processing or notifications. For example, if you need a webhook to respond in real-time to a file action, create the webhook in the same site as the triggering file action.

Actions by Child Site Users

File actions performed by child site users are always logged only within their site.

This means that notifications or automations in the parent site are never triggered by file actions performed by child site users.

Actions in the Underscore Folder on Parent Sites

When parent site administrators interact with the contents of a child site using the underscore folder, those changes are only captured in the parent site's logs, and they are not logged within the child site.

Notifications or automations in the child site cannot be triggered by file actions taken through the underscore folder on the parent site because those actions occur within the context of the parent site.

Actions in Child Site by Parent Site Users

When a parent site user connects to a child site, any actions they perform within the site are captured in the child site's logs only.

Automations configured on the underscore folder in the parent site cannot be triggered by file actions taken within a child site.