> 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/tutorials/guides/how-to-use-workflows.md).

# How to use Workflows

Workflows can help manage, structure and organize your work.

## What is a workflow?

Struct PIMs workflow engine is a powerful feature that allows you to manage, structure and organize your work within the system. A workflow consists of workflow settings and workflow states.

Workflow settings contains the alias of your workflow, and a label for the business rule. Meanwhile Workflow states contains the created [states](/reference/settings/data-governance/workflows/workflow-states.md) the workflow can be in and the [transitions](/reference/settings/data-governance/workflows/workflow-states/workflow-state-transitions.md) added between them.

Workflows can be found by navigating to data governance under "settings" and clicking on workflows.

{% embed url="<https://vimeo.com/1113483807/32fb299f5f>" %}
Workflow management in Struct PIM  (duration 03:40 min)
{% endembed %}

## Guides covering workflows

* [How to set up and edit a workflow](/tutorials/guides/how-to-use-workflows/how-to-set-up-and-edit-a-workflow.md)
* [How to use transitions in a workflow](/tutorials/guides/how-to-use-workflows/how-to-use-transitions-in-a-workflow.md)
* [How to use assignments in a workflow](/tutorials/guides/how-to-use-workflows/how-to-use-assignments-in-a-workflow.md)
* [Example of workflow](/tutorials/guides/how-to-use-workflows/example-of-workflow.md)


---

# 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/tutorials/guides/how-to-use-workflows.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.