Skip to content

Update security best practices #720

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bryantgillespie merged 1 commit into from
Jun 5, 2026
Merged

Update security best practices #720

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions content/guides/13.security/1.best-practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ Flows run arbitrary operations. They can execute custom scripts, make HTTP reque
- Grant create, update, and delete on `directus_flows` and `directus_operations` to administrators only.
- For flows with a **Webhook** trigger, treat the trigger URL as a public endpoint. Require an access token or a shared secret in the request, and validate the payload inside the flow before taking action.
- Audit any flow that contains a **Run Script** operation before enabling it. Script operations execute Node.js code with the privileges of the flow's accountability.
- A **Manual** trigger flow lists its target collections in the `options` field, potentially exposing the names of collections a user has no permission to access. To prevent this keep flows used by lower-privileged users separate from those that reference restricted collections.

### Settings

Expand Down
Loading