Child Sites History and Logging

File actions that affect a Child Site can happen on the Child Site itself or through the Parent Site's underscore folder. Each action is logged in the site where the user or process is authenticated, never both. This rule keeps logs deduplicated and prevents the same action from raising notifications in two sites.

File actions performed by users connected directly to a Child Site are logged in the Child Site only. Notifications and automations on the Parent Site are not triggered by file actions inside the Child Site, even when the Parent Site Administrator has full access to that content through the underscore folder.

File actions performed by Parent Site Administrators through the underscore folder are logged in the Parent Site only. Notifications and automations on the Child Site cannot be triggered by underscore-folder activity because those actions occur in the Parent Site's context.

When a parent-site user with delegated access switches into the Child Site, any actions they take inside the Child Site are logged in the Child Site, not the Parent Site. Switching sessions is what determines which site records the action.

Use this rule to decide where to configure downstream processing. If a webhook or automation needs to fire in response to a specific file action, create it in the same site where the action will be performed.