> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/workflow-framework/workflow-framework-overview.md).

# Workflow Framework Overview

LogicNets offers a Workflow Framework that allows for multi-user collaboration through workflows modeled in LogicNets. This framework enables users or systems to create and assign tasks based on user roles and to move those tasks through to completion depending on identified rules. This workflow functionality can be incorporated with other LogicNets frameworks as well.

To see a demonstration of the workflow functionality of the LogicNets platform, watch this short [video](/release-9/example-gallery/demo-videos/workflow-framework-example-video.md).

Click [here](/release-9/example-gallery/example-applications/workflow-framework-example-application-with-roles.md) to download the sample project that goes with the demonstration video. Once you have downloaded it you can import it into your Designer account and run it in test mode.


---

# 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/workflow-framework/workflow-framework-overview.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.