Approvals across products

Overview

Approvals in Ottili ONE are not an island feature of a single module. They are part of the same platform: an approval-first model keeps a human in control of every irreversible or externally visible action — whether that action is triggered by Ottili AI, Ottili HQ, LD3, Ottili Coder or a Flow.

This article explains how the cross-product approval model works, what each product contributes, and the rules — permissions and company-scoped isolation — that apply consistently everywhere.

One shared approval model

Instead of every product maintaining its own isolated approval flow, the modules use the same platform mechanics:

• Approval queue*: AI and Flows can prepare work freely, but anything that affects the outside world waits for an approval.
• Unified audit trail*: Every action and approval is recorded — who or what proposed it, who approved it, and when.
• Permission-controlled*: Who can approve follows the same permission model as access to the data.

What needs approval

Reversible, internal steps run automatically. Irreversible or external actions — messaging a customer, making a purchase, publishing, deploying — land in the approval queue first.

Product by product

Ottili AI

Critical AI actions are approval-first and enforced through Ottili Console and Ottili Core (live, enforced). Before AI sends anything outward, the action is presented for approval.

Ottili HQ

In Ottili HQ, AI-assisted steps and automated actions are routed through the same platform approval queue. Business objects — quotes, orders, invoices — can only act outward with an approval.

LD3

LD3 is draft/approval-first by default. Publication of external posts is held until a named approver confirms. The decision — who, when, which channel — is written onto the content package.

Ottili Coder

In Ottili Coder, approval gates hold risky or external steps (code or infrastructure changes, publishing, sending messages). The task pauses at the gate; you review, approve or reject. The decision is recorded on the run record. Approvals behave the same in local, cloud and hybrid runs.

Ottili Flows

Ottili Flows is the AI-first workflow automation engine. A Flow can include an Approval* step: it stops and asks a person before a sensitive or external step runs. Approved Flows use the same approval and audit-trail mechanism as the rest of Ottili ONE.

Permissions and company scope

Who can approve is not a separate per-module setting. It follows the shared permissions and entitlements of Ottili ONE: roles decide who can see and do what — and approval is bound to the company context (company scope), so no approval step crosses another company's data boundary.

Maturity at a glance

Related

• The [approval queue](/docs/approval-queue) — the platform foundation.
• [LD3 approvals](/docs/ld3-approvals) and [Coder approvals](/docs/coder-approvals).
• [Ottili Flows](/docs/ottili-flows) and [build a flow](/docs/build-a-flow).
• [Files across products](/docs/files-across-products) — the same cross-product principle for storage.