fix: keep fork out of is_restricted and read it from the caller's role

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Guilhem Lemouel
2026-10-22 07:36:36 -07:00
co-authored by Claude Opus 5.5
parent 8bba9e92f9
commit 304279f73e
5 changed files with 32 additions and 12 deletions
+1 -1
View File
@@ -19,7 +19,7 @@ code is `windmill_common::roles`.
| `flows` | `none` / `compose` / `full` | yes |
| `apps` | `none` / `compose` / `full` | yes; low-code apps and worker-built apps need `full` |
| `manage_schedules`, `manage_triggers` | bool | yes, see `docs/operator-write-rights.md` |
| `fork` | bool | yes: both fork endpoints; the forker is a developer in the fork, see `docs/operator-write-rights.md` |
| `fork` | bool | yes: both fork endpoints, read with `caller_role_capabilities`; the forker is a developer in the fork, see `docs/operator-write-rights.md`. Like visibility, not part of `is_restricted` |
| `visibility.*` | bool per page | no, UI only |
`compose` is the former operator builder right: the composition-only checks of