# Workflows ### Overview As part of the **Functional Architecture**, the **Workflows** section describes the workflow module in OpenCRVS — how records move through the system and how users interact with them at each step. It is organised into the following modules: * **Administrative Structure** — * **Users** — describes how user roles, scopes, and jurisdictions determine who can see which records and perform which actions in a workflow. * Jurisdictions * **Actions** — explains the building blocks of workflows: the actions users can take on a record (for example, Notify, Declare, Register, Correct), how actions change status and flags, and how custom actions are configured. * **Workqueues** — covers how records are surfaced to users as work items, using filters, assignment, and queue configuration to support day-to-day operations (review, validation, approval, certification). * **Offline working** — describes how users can continue workflow steps when offline, including assignment, Outbox behaviour, and how offline actions are synchronised and audited. * **Deduplication** — explains how OpenCRVS detects and manages potential duplicate records, and how review actions (Mark as duplicate / Mark not duplicate) fit into the overall record workflow. * **Comms** — describes how communications (SMS, email) are triggered from actions in the workflow, for example sending notifications to informants when a record is registered, rejected, or requires correction. These modules together show how to translate country business rules into concrete, action-driven workflows in OpenCRVS. --- # 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://documentation.opencrvs.org/v2.0/functional/markdown/workflows.md?ask= ``` 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.