Global actions
Some actions belong to one template. Others - open the folder in your editor, initialise a repository, tag every arriving PDF - belong to the way you work. A global action is written once and can be attached to any template in your library.
Defining one
Globals is the third entry in the sidebar, beside Library and Settings. Its Automation tab holds the global actions and edits them with the same editor a template uses: a name, a trigger, a type and its settings, with the same Enabled switch.
Both triggers are available, so a watching rule can be global too - a "Tag as Draft" or a "Sort by kind" you attach wherever it is wanted rather than rebuilding it in each template.
Using one in a template
Select a folder or file in a template's Structure tab and choose Add Action. The picker lists the template's own actions first, then everything in the library under a Globals heading, each marked with a small globe.
Select a folder or file in a template's Structure tab and choose Action in the toolbar below the canvas. Everything you can attach is listed together with a checkbox each, the template's own actions and the library's in one list, and the ones already attached are ticked. Each row shows the action's name above what it does.
Attaching a global does not copy it. The template points at the one definition, so editing it in Globals changes every template that uses it. That is the reason to make an action global, and the reason to think before editing one.
When a template has its own copy
A template's own definition always wins. If a template carries its own copy of an action and a global with the same identity exists, the deploy uses the template's copy and behaves exactly as it did before that global was created.
The picker follows the same rule and leaves that global out, so you are never offered the same action twice.
Deleting a global that templates are still attached to does not silently change what they do. The deploy reports that the shared action is missing rather than falling back to something else.
Sharing them
A .prefab file carries the global actions its templates rely on, meaning the ones the templates
attach without defining themselves. See Sharing templates for the file format.
On the receiving MacPC, a global the library already holds is left exactly as it is, and anything new is added under the same identity it was exported with. That matters because a template attaches an action by its identity rather than by its name: giving the incoming action a new one would break the link the file was carrying it for. Global placeholders are matched by key instead, which is why the two behave differently on import.