POST /api/workflows is open to any employee, but PUT/DELETE are admin-only and the Edit button (the only way to read a definition in the UI) is hidden for non-admins. An employee who makes a typo in a workflow they just created is stuck; they also cannot inspect what an existing workflow will do before pressing Execute.
Suggested fix
Add a read-only View definition modal for everyone (steps list rendered human-readably).
Allow the creator to edit/delete their own workflows, or make creation admin-only for consistency.
## Overview
`POST /api/workflows` is open to any `employee`, but `PUT`/`DELETE` are admin-only and the Edit button (the only way to *read* a definition in the UI) is hidden for non-admins. An employee who makes a typo in a workflow they just created is stuck; they also cannot inspect what an existing workflow will do before pressing Execute.
## Suggested fix
- Add a read-only **View definition** modal for everyone (steps list rendered human-readably).
- Allow the creator to edit/delete their own workflows, or make creation admin-only for consistency.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Overview
POST /api/workflowsis open to anyemployee, butPUT/DELETEare admin-only and the Edit button (the only way to read a definition in the UI) is hidden for non-admins. An employee who makes a typo in a workflow they just created is stuck; they also cannot inspect what an existing workflow will do before pressing Execute.Suggested fix