> ## Documentation Index
> Fetch the complete documentation index at: https://api-docs.ollang.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows and Provider Architecture

> Understand workflow configuration, provider orchestration, language-pair logic, and AI provider selection inside the Ollang Project Management Dashboard.

## Overview

Workflows inside the Ollang Project Management Dashboard determine:

* how Orders are processed,
* which providers are used,
* which AI models are selected,
* how language pairs are configured,
* and how localization pipelines operate.

A Workflow is a reusable operational configuration that defines how localization should happen for a specific language pair.

Example:

```text theme={null}
English → French

CC / Transcription:
Ollang Agentic

Subtitle Translation:
OpenAI

AI Dubbing:
Gemini TTS
```

This allows organizations to:

* standardize localization workflows,
* benchmark provider quality,
* optimize costs,
* and maintain consistency across multilingual operations.

***

# What is a Workflow?

A Workflow is a reusable configuration that determines:

* which providers are used,
* which language pair is localized,
* how localization is processed,
* and how Orders are operationalized.

Instead of manually selecting providers every time, organizations can:

* preconfigure workflows,
* reuse them across Orders,
* and standardize operational quality.

<Frame>
  <img src="https://mintcdn.com/ollang/a4ucNOBUQRWRvsN6/images/b1.png?fit=max&auto=format&n=a4ucNOBUQRWRvsN6&q=85&s=a7003c17a4b3b7a1a295a889c119a708" alt="B1" width="2452" height="606" data-path="images/b1.png" />
</Frame>

<Frame>
  <img src="https://mintcdn.com/ollang/a4ucNOBUQRWRvsN6/images/b2.png?fit=max&auto=format&n=a4ucNOBUQRWRvsN6&q=85&s=3388ba831f16c2f0cb5639d996d417e7" alt="B2" width="1656" height="702" data-path="images/b2.png" />
</Frame>

# Workflow Scope

Workflows can currently be configured at:

<CardGroup cols={2}>
  <Card title="Global Workflow" color="#6148f9" icon="globe">
    Default workflow configuration applied across the organization.
  </Card>

  <Card title="Folder-Level Workflow" color="#6148f9" icon="folder">
    Folder-specific workflow configuration overriding global settings.
  </Card>
</CardGroup>

<Info>
  Project-level workflows are not currently supported. Workflows can be configured globally or at the Folder level.
</Info>

***

# Global Workflows

## Overview

Global workflows act as:

* organization-wide default workflows.

These workflows automatically apply when:

* no Folder-level workflow exists.

Example:

```text theme={null}
Global Workflow

English → French

CC:
Ollang Agentic

Subtitle Translation:
OpenAI

AI Dubbing:
ElevenLabs
```

This becomes:

* the operational default for all applicable Orders.

***

# Folder-Level Workflows

## Overview

Folder-level workflows allow teams to configure localization differently for specific operational use cases.

This is useful when:

* different teams require different providers,
* different content types require different quality standards,
* or experimentation is needed.

Example:

```text theme={null}
Folder A

English → French

CC:
Speechmatics

Subtitles:
Open AI

AI Dubbing:
Gemini
```

```text theme={null}
Folder B

English → French

CC:
Ollang Agentic

Subtitles:
Ollang Agentic

AI Dubbing:
ElevenLabs
```

Even though:

* the language pair is identical,

the workflow may differ depending on:

* operational requirements,
* content type,
* and quality expectations.

<Frame>
  <img src="https://mintcdn.com/ollang/a4ucNOBUQRWRvsN6/images/b3.png?fit=max&auto=format&n=a4ucNOBUQRWRvsN6&q=85&s=cc2b851be2ceedcd6a26bfa3d0413e7e" alt="B3" width="770" height="304" data-path="images/b3.png" />
</Frame>

<Frame>
  <img src="https://mintcdn.com/ollang/a4ucNOBUQRWRvsN6/images/b4.png?fit=max&auto=format&n=a4ucNOBUQRWRvsN6&q=85&s=3520951d64d68c8732178c35f24ece37" alt="B4" width="2534" height="810" data-path="images/b4.png" />
</Frame>

# Workflow Override Logic

Folder-level workflows always override:

* Global workflows.

Hierarchy:

```text theme={null}
Folder-Level Workflow
        ↓
Global Workflow
```

Example:

```text theme={null}
Global:
English → French → Provider A

Folder:
English → French → Provider B
```

Result:

```text theme={null}
Folder Workflow is used.
```

***

# Workflow Architecture by Order Type

Different workflows can be configured independently for different localization stages.

Supported workflow categories include:

<CardGroup cols={2}>
  <Card title="Video Captioning (CC)">
    Speech-to-text and caption generation workflow.
  </Card>

  <Card title="Subtitle Translation">
    Translation workflow for multilingual subtitle localization.
  </Card>

  <Card title="AI Dubbing">
    Voice synthesis workflow including Lip Sync and Audio Description.
  </Card>

  <Card title="Document Translation">
    Localization workflow for structured and document-based content.
  </Card>

  <Card title="Studio Dubbing">
    Workflow coordination for studio-managed dubbing operations.
  </Card>
</CardGroup>

***

# Multiple Workflows for the Same Language Pair

Organizations may configure multiple workflows for the same language pair across different Folders.

Example:

```text theme={null}
Folder A

English → French
CC: Ollang Agentic
Subtitles: Provider A
Dubbing: Gemini
```

```text theme={null}
Folder B

English → French
CC: Speechmatics
Subtitles: Provider B
Dubbing: ElevenLabs
```

This enables:

* benchmarking,
* experimentation,
* quality optimization,
* and use-case-specific localization.

***

# Provider Architecture

## Overview

Ollang acts as an orchestration layer. Rather than forcing a single provider, the platform enables organizations to:

* choose providers,
* benchmark providers,
* compare results,
* and optimize workflows.

This creates operational flexibility because:

```text theme={null}
The best provider today
may not be the best provider tomorrow.
```

Organizations can continuously optimize workflows based on:

* quality,
* cost,
* speed,
* and content type.

***

# Speech-to-Text (STT) Providers

Speech-to-text providers are commonly used for:

* Video Captioning,
* transcription,
* subtitle generation,
* and speaker diarization.

Supported examples include:

<CardGroup cols={2}>
  <Card title="Ollang Agentic">
    Recommended orchestration-first workflow optimized for flexibility.
  </Card>

  <Card title="Speechmatics">
    Commonly used for multilingual speech recognition.
  </Card>

  <Card title="AssemblyAI">
    Speech-to-text provider for transcription workflows.
  </Card>

  <Card title="AWS">
    Enterprise-oriented transcription workflow option.
  </Card>
</CardGroup>

***

# Translation Providers

Translation providers are used for:

* subtitle translation,
* document translation,
* multilingual localization,
* and AI-assisted language generation.

Examples include:

<CardGroup cols={2}>
  <Card title="Ollang Agentic">
    Recommended orchestration workflow for multilingual localization.
  </Card>

  <Card title="OpenAI">
    LLM-based multilingual translation workflows.
  </Card>

  <Card title="Claude">
    Translation workflow for reasoning-intensive localization tasks.
  </Card>

  <Card title="Gemini">
    Multilingual translation and contextual language generation.
  </Card>
</CardGroup>

***

# Text-to-Speech (TTS) Providers

TTS providers are used for:

* AI Dubbing,
* Audio Description,
* voice synthesis,
* and multilingual speech generation.

Supported examples include:

<CardGroup cols={2}>
  <Card title="ElevenLabs">
    Commonly used for multilingual voice generation and dubbing workflows.
  </Card>

  <Card title="Gemini TTS">
    Used for controllable voice prompting and expressive delivery.
  </Card>

  <Card title="Azure TTS">
    Enterprise voice synthesis option.
  </Card>
</CardGroup>

***

# Workflow Lifecycle

## Important Operational Rule

<Warning>
  Workflow updates only affect future Orders.
</Warning>

Already-created Orders:

* remain unchanged,
* preserve their operational workflow,
* and continue using the workflow selected at Order creation.

***

# AI Quality Benchmarking

Organizations commonly benchmark providers using:

* AI QC Evaluation,
* Human QC Annotation,
* analytics,
* and localization performance tracking.

This helps teams understand:

```text theme={null}
Which provider works best
for which language pair,
content type,
or workflow.
```

Because the AI ecosystem evolves rapidly:

```text theme={null}
The best-performing provider today
may not remain the best tomorrow.
```

The platform is intentionally designed for:

* experimentation,
* optimization,
* and provider flexibility.

***

# Example Enterprise Workflow

```text theme={null}
English → French

CC:
Ollang Agentic

Subtitle Translation:
OpenAI

AI Dubbing:
Gemini TTS

QC Evaluation:
Enabled
```

***

# Example Multi-Folder Benchmarking

```text theme={null}
Folder A → Marketing Content
English → French
Dubbing: Gemini
```

```text theme={null}
Folder B → Entertainment Content
English → French
Dubbing: ElevenLabs
```

Teams can later compare:

* localization quality,
* human edit percentage,
* QC outcomes,
* and operational performance.

***

# Important Operational Notes

<AccordionGroup>
  <Accordion title="Can workflows be configured at Project level?">
    No. Workflows can currently be configured at Global level and Folder level only.
  </Accordion>

  <Accordion title="Do Folder-level workflows override Global workflows?">
    Yes. Folder-level workflows always take precedence.
  </Accordion>

  <Accordion title="Can organizations configure multiple workflows for the same language pair?">
    Yes. Different Folders may use different workflows for the same language pair.
  </Accordion>

  <Accordion title="Do workflow changes affect existing Orders?">
    No. Workflow updates only affect future Orders.
  </Accordion>

  <Accordion title="Can providers be selected independently for CC, Subtitle Translation, and AI Dubbing?">
    Yes. Different workflow stages can use different providers.
  </Accordion>

  <Accordion title="Does Ollang force one provider?">
    No. Ollang acts as an orchestration layer and allows organizations to choose providers based on operational goals.
  </Accordion>
</AccordionGroup>