# Workflow Model

<figure><img src="/files/Q15y2jZivWOT0iiDbNYW" alt=""><figcaption></figcaption></figure>

### What is a workflow?

A workflow is a unique configuration of various interconnected Inverter Protocol contracts, designed to achieve a specific goal. It functions like a blueprint, detailing the roles and interactions of different components and modules, allowing for customized solutions tailored to diverse use cases and requirements.

### Components of a Workflow

In practical terms, a workflow in the Inverter Protocol involves a core Orchestrator contract that coordinates and directs activities among specialized modules like the Funding Manager, Authorizer, Payment Processor, and Logic Modules.

Additionally, Factories play a crucial part as they facilitate the permissionless deployment of all contracts within a workflow.

Each type within the workflow model performs dedicated functions:

* **Factories**: Allow for permissionless deployments of all the contracts of the workflow.
* **Orchestrator**: The central contract that holds the references to all integrated modules and allows for the addition and removal of other modules into the workflow.
* **Funding Manager**: Contains the funds of the workflow that can be accessed by other modules. Based on which module fills this role the funding manager can handle user deposits and withdrawals, as well as take on the role of a Primary Issuance Market (PIM).
* **Authorizer**: Controls access and permissions within the workflow, ensuring that only authorized users and modules can perform certain actions.
* **Payment Processor**: Handles the outgoing token flows of the workflow based on so-called payment orders.
* **Logic Modules**: This category includes the remaining modules in the system. They implement the specific business logic a user may wish to apply to their contract, such as requesting funds from the Funding Manager, creating payment orders, or performing any other tasks they are designed to do.

### Security and Governance

The security of modules is critical to the entire workflow. All contracts undergo rigorous [security audits](/concepts/protocol-concepts/security/audits.md) and continuous reviews to ensure their integrity and safety. Updates and modifications to the modules are managed through established [governance](/concepts/protocol-concepts/governance.md) mechanisms, involving community input and decentralized decision processes.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inverter.network/concepts/protocol-concepts/workflow-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.