Manual flows may cause security risks that the user isn't aware of about directus

[SeanDylanGoff]

Misconfigured flows (and extensions) can definitely pose a security risk if permissions are not properly checked. The general rule of thumb is dont expose admin features to non-admin users unless you're certain the flow/extension is "safe" to do so.

the problem is that i believe most users will not realise that a manual flow is NOT restricted to admins (even though it's ONLY shown to admins in the app), but actually PUBLIC!

basically i'm arguing that a large part of flows created are "misconfigured" security wise without the creator realising.

[shipsides-sparknel]

the platform philosophy of being agnostic to this type of configuration is supported by the inclusion of $trigger.accountability on manually fired flows:

this way, it's up to the author of the flow to implement as much or as little security as they want.

you can also enable/restrict visibility of specific flows within the app by changing a role's read permissions to the id's within directus_flows

[br41nslug]

Misconfigured flows (and extensions) can definitely pose a security risk if permissions are not properly checked. The general rule of thumb is dont expose admin features to non-admin users unless you're certain the flow/extension is "safe" to do so.