Managing Automations

Managing automations is straightforward with several available options. Site Administrators or Folder Admins can modify, enable or disable, clone, rename, run, or delete automations.

Automation Access and Permissions

Accessing and managing automations depends on whether a user is a Site Administrator or a Folder Admin, which determines what automations they can create, edit, run, and view.

Site Administrators

Site Administrators have full access to automations across the site, including automations that reference folders on the site, remote servers, and child sites. They can create, manage, edit, and run all automations, including automations created by other Site Administrators and Folder Admins.

Folder Admins

Folder Admins can create automations for folders where they have admin permissions. For example, a Folder Admin can create move or copy automations when both the source and destination folders are folders they administer.

Folder Admins can manage, edit, and run automations associated with folders they control.

Folder Admins can see automations when all folders referenced by the automation are folders where they have admin permissions. Visibility does not imply ownership or execution log access.

Folder Admins can use wildcards in source and destination paths when creating or editing automations. Wildcards can make an automation appear to cover broader paths, but they do not grant additional folder access. Actual folder access is enforced at runtime using the permissions of the automation owner.

Runtime Permission Evaluation

Automations always run using the permissions of its current owner. An automation can read from or write to only the locations the owner is authorized to access, regardless of who created the automation or how it is configured. Changes to ownership can affect runtime behavior and reliability.

Modifying an Automation

You can modify automations to adjust the automation triggers, actions, file or folder name matching patterns, customizations, and folder paths directly from the Automations home page or details page.

Modifying an automation can change its ownership, with implications for permissions and reliability.

Enable or Disable an Automation

Enabling or disabling automations is straightforward from the Status column or details page, allowing you to pause and resume them as needed. Once disabled, all future runs of the automation will stop immediately, regardless of triggers or actions, but you can always re-enable it later.

Clone an Existing Automation

Cloning automations helps you to duplicate and customize them for various sources, destinations, or triggers, providing flexibility in adapting processes to different scenarios or requirements. Cloned automations are in a disabled state by default.

Using Run Now for Instant Execution

For immediate testing or execution, the Run now option is available for enabled automations, providing instant results.

Deleting an Automation

Deleting automations is also simple, though note that once deleted, they cannot be restored and all future runs will be stopped.

Automations with Child Sites

Site Administrators use the underscore folder to create automations that interact directly with child sites. Each parent site automation that moves or copies can use child site folders as the source, destination or both. Automations in parent sites can create folders or delete files from folders on the parent site or any child sites.

Every automation belongs to only 1 site, and it can only be managed through its site. Even when a parent site automation uses a child site for source or destination folders, the automation and its run logs exist within the parent site.

Automations in child sites have no way to interact with parent sites or any other child sites.