Data and Automations Across Child Sites

The Parent Site reaches Child Site content through the underscore folder. Automations and Syncs belong to the site where they are configured, even when they process another site's files. Their file actions through the Parent Site's Child Site folders are recorded on both sites, allowing each site to run its own downstream processing.

Transferring Files Between Parent and Child Sites

Parent Site Administrators can move or copy files between the Parent Site and any Child Site by choosing a Child Site folder as the source or destination. They can also move or copy files between two Child Sites by working through both sites' folders under the Parent Site's underscore folder.

These transfers use the Child Site's ordinary folders at _/Sites/<child-site-id>, including Remote Server Mounts configured in those folders. The Child Site's own system-controlled _ folder and its contents are outside this view and cannot be used as cross-site sources or destinations. The same boundary applies to Parent Site Automations and Syncs. Child Site Folders explains which features require access directly in the Child Site.

Users logged in directly to a Child Site cannot move or copy files to the Parent Site or to any other Child Site. Cross-site file movement runs through the Parent Site only.

The Child's Folder Settings govern transfers into its folders, including GPG, Auto Unzip, Malware Scanning for uploads, filename restrictions, and retention. The Parent's file-processing and retention settings do not carry through the view.

Archive Only Mode on either Site protects the files, and each Site's administrator lock bypass relaxes only its own locks. Access Across Sites and Storage explains these boundaries for transfers, Automations, and Syncs.

Automations with Child Sites

A Parent Site Administrator can create automations on the Parent Site that interact with Child Sites through the underscore folder. In v1, a Move, Copy, Create Folder, or Delete automation on the Parent Site can target a folder within the Child Site's folder tree for its source, destination, or both.

V2 provides the corresponding action nodes, with access determined by its site or Workspace ownership.

Every Automation belongs to one site and is managed only through that site. A Parent Site Automation that targets a Child Site folder still lives in the Parent Site, and its run logs remain there. The file actions it produces through the underscore folder appear in both the Parent Site's and the Child Site's History.

File Action Triggers and Child Sites

File Action triggers in v1 and v2 respond to file actions recorded in the Automation's own site when the action, path, and other conditions match.

Activity through the Parent Site's Child Site folder is recorded on both sites. A Parent Site Automation watches the _/Sites/<child-site-id>/... path; a Child Site Automation watches the corresponding path within the Child Site.

For example, when the Parent Site uploads a file into a Child Site's intake folder, Automations on either site can respond to that upload. Activity performed directly within the Child Site is recorded there only, so it can trigger a Child Site Automation but not a Parent Site Automation.

A Child Site Automation processes only that Child Site's folders; it has no access to the Parent Site or sibling Child Sites. Receiving a file event from a Parent Site operation does not extend that access.

Configure webhooks and Automations on the site responsible for the response, using that site's paths and recorded actions. Child Site History and Logging explains the records for cross-site copies and moves and the distinction between file History and workflow run logs.

Syncs with Child Sites

Parent Site Administrators can create Syncs on the Parent Site that target Child Site folders as the source, destination, or both. The Parent Site can sync from itself to a Child Site, from a Child Site to itself, or between two Child Sites.

Syncs in a Child Site can only move files between folders inside the same Child Site. A Child Site Sync has no way to reach the Parent Site or any sibling Child Site.

The Sync's run logs remain in the site where it is configured. File actions performed by a Parent Site Sync through a Child Site folder are recorded in both sites' History and can trigger each site's matching notifications, webhooks, and Automations.

Using API Keys with Child Sites

API keys are linked to one site. A key issued on the Parent Site authenticates only against the Parent Site. A key issued on a Child Site authenticates only against that Child Site. Site-wide and per-user API keys both follow this rule.

When a script or integration needs to operate across the Parent Site and one or more Child Sites, issue a separate API key on each site and have the integration switch between them.