AI capture & automations

Inbox and drive files become reviewable drafts — AI capture that posts only when you approve.

What you get

Email & drive capture — Forward or drop files; recipes extract into the right draft.
Approve before it posts — Automation prepares; operators confirm money and masters.
Usage you can explain — AI spend rolls up per workspace — not a surprise invoice.

Does AI post journals by itself? No — capture creates drafts; posting waits on approval.

Automations prepare bills, expenses, or candidates. A person with permission confirms before money or masters change.

Which inboxes can we connect? Gmail, Microsoft 365, and Google Drive are first-class sources.

Sources are workspace-scoped. Operators choose which mailboxes and folders may feed recipes.

Is this a generic RPA toy? No — recipes target Omnizone documents and HR intake.

Extraction maps into bills, expenses, leads, employees, and similar records your team already uses.

How does Ask relate to automations? Ask answers and proposes commands; automations ingest files on a schedule or push.

Both check the same permissions. Neither dumps raw schema or bypasses role grants.

Can HR use capture without seeing company cash? Yes — HR recipes stay behind HR grants; finance stays behind finance grants.

Role isolation matches the rest of Omnizone: payroll access is not company available cash.

What if extraction is wrong? Reject or edit the draft — nothing silent posts.

Runs keep the source file so you can see why a field was suggested.

No — drafts wait for an operator with permission before they hit the ledger or masters.

Gmail, Microsoft 365, and Google Drive connectors feed the recipe gallery.