> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/changelog/february-2026/february-20th.md).

# February 20th

**Changelog released on 2026-02-20**

Welcome to this release. We’ve added a new permission to control who can transition workflow states on entities. Administrators can now assign this permission to specify which users are allowed to change entity workflow states.

## Task

1. **Add a new permission to control who can transition workflow states on entities:** Separated the permission to create, edit and delete workflows from the permission to transition between workflow states on entities. The permission ‘Manage Workflows’ now controls who can create, edit and delete workflows while the permission ‘Transition Workflows’ control who can transition workflow states on entities. (SP-2236)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.struct.com/changelog/february-2026/february-20th.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.