What functionality is supported by Flow Designer?

Flows cannot typically be run as `security_admin` directly for general operations; they usually run as the system user or the user who initiated them, or with specific impersonation that doesn't usually include `security_admin`.

Flows primarily trigger on record creation or update, but generally do not trigger directly on a record being deleted due to technical complexities where the record may no longer exist to query.

Flow Designer allows for the creation of subflows, which are reusable sequences of actions, and these subflows can be called and executed from within a larger main flow, promoting modularity and efficiency in automation.

The `flow_operator` role is for monitoring and troubleshooting flows, not for creating and editing them; the `flow_designer` role is required for creation and editing.