Configure a Global Export Action¶

Add a Global Export action to export data that belongs to the whole organization, check templates or the Access Report, into an enrichment datastore whenever the Flow's trigger activates. Combined with a Schedule trigger, it takes a recurring snapshot, such as a weekly access review. To export a single datastore's anomalies, quality checks, or field profiles instead, see Configure an Export Action.

Permission Required

To edit and publish a Flow, you need the Editor team permission on every datastore it relates to. Admins are exempt. The destination enrichment datastore counts as one of them. On top of that, exporting Check Templates needs the Manager role, and a Flow that contains a Global Export of the Access Report goes further: only users with the Admin role can create, edit, delete, or manually execute it. See Flow Permissions for details.

Enrichment datastores only

The destination must be an enrichment datastore. Global exports do not read from a source datastore, so no source or enrichment link is involved.

Field reference¶

Field	Type	Description
Asset Type	Option	What to export. See Asset types.
Enrichment Datastore	Option	The enrichment datastore the export is written to.
Check Templates	Multi-select	Only shown for Check Templates. The templates to export. Leave it empty to export every template, including ones created after the action is saved.

Asset types¶

Option	Description
Check Templates	Exports the Library's check templates to `_export_check_templates`, the same output as Export Check Templates. Managers and Admins can configure it.
Access Report	Exports every active user's effective team permission on every datastore they can access to `_export_user_permissions`. See Export Outputs for its columns. Always a full snapshot. Only Admins can configure it.

The columns of both outputs are on Export Outputs. Each run replaces the output with a fresh export, stamped with its GENERATED_AT timestamp.

How the action runs¶

It waits for the export. The action starts a Global Export operation in the enrichment datastore and stays running until that operation finishes. It then ends with the export's own result, Success or Failure, so actions chained after it run only once the export has succeeded.
The run is tracked. The operation appears in the enrichment datastore's Activity tab like any other run. Aborting the Flow execution aborts the export.
Notifications after it get operation tokens. A notification chained after a Global Export action offers the same tokens as one chained after an Operation action, such as {{operation_type}}, {{operation_result}}, and {{target_link}}. See Message.
It fails early if the target is gone. If the destination no longer accepts enrichment writes, or a selected check template was deleted, the action fails without starting an export, and the actions after it are skipped.

Steps¶

Step 1: Navigate to the Flows page by clicking Flows on the left side panel.

Step 2: On the Definitions tab, click the Flow. On its canvas, click the dashed Action placeholder after the trigger, or the + handle at the bottom edge of a node.

Step 3: In the List of Actions panel, pick the Operation category, then click Global Export. Its settings panel opens on the right-hand side.

Step 4: Fill in the fields.

Step 5: Click Save. The node shows a CHANGED badge and the You have unpublished changes banner appears on the canvas.

Step 6: Click Publish to make the action live.

For a complete Flow built around this action, see the Weekly Access Review example.