> For the complete documentation index, see [llms.txt](https://docs.fortifiedid.se/control/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortifiedid.se/control/overview.md).

# Overview

Overview of Fortified ID Control

Fortified ID Control helps organizations **digitalize business processes** that would otherwise be handled manually. Instead of relying on emails, spreadsheets, separate admin tools, and repeated support tasks, organizations can build controlled flows for requests, approvals, automation, and follow-up actions in one place.

This makes it possible to **replace manual routines** with structured and traceable processes, **improve efficiency** for both IT and business users, and **reduce operational cost** over time. It can also **improve security** by reducing the human factor in sensitive tasks and by introducing controlled **request-and-approve flows** before access is granted or changes are applied.

Control is used to build and operate digital process flows, self-service experiences, and automation across connected systems. For practical examples of what the product is capable of, see [Common Use Cases](/control/common-use-cases.md).

## Why Fortified ID Control?

* Digitalizes business processes that are otherwise handled manually
* Replaces manual routines with structured and repeatable workflows
* Improves efficiency for both business users and IT
* Lowers cost by reducing administrative overhead and support effort
* Improves security through controlled workflows, approvals, and reduced human error

## Key components in Control

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Pipes</strong><br>Workflow logic, automation, and integrations</td><td><a href="/control/key-components/pipes.md">Pipes</a></td></tr><tr><td><strong>Forms</strong><br>Interactive flows, steps, and controls</td><td><a href="/control/key-components/forms.md">Forms</a></td></tr><tr><td><strong>API</strong><br>Exposing controlled endpoints to other systems</td><td><a href="/control/key-components/api.md">API</a></td></tr><tr><td><strong>Schedules</strong><br>Recurring background jobs</td><td><a href="/control/key-components/schedules.md">Schedules</a></td></tr></tbody></table>

## Where to go next

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Getting Started</strong><br>The first steps after choosing Control</td><td><a href="/control/get-started.md">Getting Started</a></td></tr><tr><td><strong>Common Use Cases</strong><br>Business-oriented and hands-on examples</td><td><a href="/control/common-use-cases.md">Common Use Cases</a></td></tr><tr><td><strong>Key components</strong><br>The main building blocks</td><td><a href="/control/key-components.md">Key components</a></td></tr><tr><td><strong>Management Center</strong><br>Product-level management and Control-specific configuration</td><td><a href="/control/management-ui.md">Management Center</a></td></tr><tr><td><strong>Configuration reference</strong><br>Runtime module details</td><td><a href="/control/configuration-reference.md">Configuration reference</a></td></tr></tbody></table>