Approvals and delegation

• "Pending Approvals" on Home — one widget that gathers what is waiting in every app you have turned on. "Open the approval inbox" in the notifications menu also brings you here.
• Action cards in the AI chat — changes the AI proposes in the chat are decided right there on the card with "Approve", "Reject" or "Skip".
• App dashboards — for example, the Knowledge dashboard can hold the "Pending Proposals" widget.

"Pending Approvals" only shows the kinds of items you can work with. Approvals that belong to a brand or site appear while that brand is selected.

"Pending Approvals" lists items of kinds like these, and you can filter by kind.

• AI action awaiting approval — the AI tried an action that goes outside and was stopped
• AI delegation review — the periodic look back at what was done under a mandate
• Knowledge proposal — proposals to add or change knowledge
• Derived relation — candidate links between pieces of knowledge
• Extraction — knowledge candidates pulled out of your material
• Workflow awaiting approval / Automation awaiting approval
• Website growth decision — decisions about growing the site
• Migration candidate — candidates from a site migration
• Inbound lead — new prospects that came in
• Support learnings — lessons learned in support
• Case read as junk — support cases that were read as junk

Large batches of similar, high-confidence candidates are handled together rather than listed one by one. Items that do need individual review say why ("Why it reached individual review" — low AI confidence, possible overlap with existing meaning, and so on).

Click a row in "Pending Approvals" to open a card with the details.

• It shows "Why (rationale)", "What this approval does", "Origin" and "What was asked".
• "Get a recommendation" shows the AI's recommendation (approve, reject, merge or hold) and its reasons. A recommendation is for reference; you decide.
• Decide with "Approve", "Deny" or "Skip". A reason is required to deny. Skip only postpones: the item comes back when the page reloads.
• When similar items come as a bundle, you can approve or reject just the ones you select. Unticked items stay pending.

Once approved, each kind is processed by its own fixed procedure. What runs is predetermined code, not the AI.

This screen lets you hand over actions that go outside or cannot be undone (sending, publishing, money, deleting) with a scope, a budget and an end date, instead of approving them one at a time. Open it from "AI delegation" under "Global". Anything not handed over still needs a person's approval every time.

There are three kinds of delegate.

• Flows (automations and workflows) — each lists the outward actions written in its definition, with the mandate's state: "Not delegated", "Active", "Stopped" and so on.
• API keys and external AI — choose what to delegate from the actions that were stopped.
• Your AI chat

Press "Delegate" to write a mandate.

• Actions to delegate — only the ones you tick. Actions that handle keys, sign-in or permissions cannot be delegated.
• Budget — the maximum number of calls per period (1 day, 1 week, 30 days).
• Valid for — up to 90 days; it does not renew by itself.
• Limits (optional) — only approved templates, quiet hours, a cap on recipients and so on.
• Objective (optional), automatic stop conditions and a review cycle.

A mandate only passes on a narrowed part of the permissions the person granting it already holds.

The "AI delegation" screen is shown to Admins and Owners.

• Only Owners can delegate, change the conditions, resume or revoke. The AI cannot issue a mandate to itself.
• Stopping is not limited to Owners. In an emergency, "Stop all delegation" stops every mandate at once, and while it is stopped every outward action waits for approval. Only an Owner can resume.
• If the person who granted a mandate leaves the tenant or loses the permission for that action, the mandate stops working.

An action outside a mandate is not run; it stops and is recorded as awaiting approval. The card gives the reason as "Outside the mandate (reason: …)". The main reasons are:

• There is no mandate
• The budget is used up
• The mandate has expired
• It is within the quiet hours
• The flow's definition changed after it was delegated (it must be delegated again)
• A flow started by the AI cannot use a mandate

A mandate stops by itself on an unusual volume, a spike in failures, a spike in opt-outs or blocks, or a drop in the objective's measure. The conditions can be loosened but not switched off, and only a person can resume a mandate that stopped itself.

"Mandate reviews" lists, at each review cycle, only the facts of what was done under the mandate. You choose "Keep going" or "Stop the mandate".

"Delegate this?" offers drafts for actions you approved 5 or more times in 14 days without a single rejection. Opening a draft hands nothing over; a person still decides.