Product Update - August 25, 2026

Multi-table Mini Apps — Build custom business apps that span multiple related tables

App Builder's composed mini apps now support multiple related tables in a single app. Previously each mini app was limited to one table; apps requiring a second table — an asset register alongside a loan log, or a vehicle fleet alongside a trip log — had to span two separate apps with no structural connection between them.

With multi-table support (schema v4), an app can define parent and child tables with typed references between them, resolve lookup values across tables, show cross-table rollup metrics and badges, and carry linked demo data that arrives pre-connected on install. Two updated platform templates showcase the new capability: Equipment Loans v5 (a Loans table backed by an Equipment register, with approval gating for loans over a threshold) and Fleet & Trip Log (vehicles and trips as linked tables with rollup mileage and status transitions). The AI assistant can also now read, describe, and perform quick updates across all tables in a mini app through the new Mini Apps agent domain.

Use case: A facilities team sets up an Equipment Loans app with an Asset register as a second table — staff submit loan requests tied to a specific asset, managers approve, and the dashboard card shows how many items are currently out on loan.

Available in: App Builder / Power Tables → Compose → Multi-table plan

---

Leader Rounds v4 — Strategic pillars, stoplight board reports, pacing quotas, and upward delegation for rounding programs

Leader Rounds adds four major capabilities in this release, collectively giving organizations a structured way to connect individual rounding conversations to strategic priorities and share results with broader audiences.

Strategic pillars let admins define the themes — Safety, Service, Quality, People, and so on — that matter to the organization. Each rounding template question is tagged to a pillar, and issues raised during rounds carry that attribution forward automatically. Stoplight board reports aggregate the pillar-level picture for a period: a leader authors a narrative for each pillar (with an AI-drafted starting point), the platform derives red/amber/green status from the underlying data, and the published report is available as a PDF for board presentations. Cadence-based pacing breaks annual rounding targets into monthly installments and shows leaders how many rounds they still have left this period, with a reframed digest email ("1 of your 3 for August still to go") instead of a raw due count. Upward delegation lets a leader transfer their rounding obligation to a manager above them — useful when a director covers an absent manager's rounds — with the obligation and attribution following the delegated leader's own reporting chain.

Use case: A CNO at a healthcare system uses stoplight board reports to present a pillar-by-pillar rounding summary to the board each quarter, with AI-drafted narratives reviewed and confirmed before publish — without any names or identifying information in the exported PDF.

Available in: Leader Rounds → Pillars · Board Reports · Team · Delegations

---

Mango Spend Analytics — Spend analytics now covers company cards, invoices, and pre-approvals, not just reimbursements

The Spend Analytics page previously computed every figure from expense reports alone. Organizations using company cards or vendor invoices saw none of that activity on the page meant to show where money was going. The page now includes an Overview plus a dedicated tab for each enabled record type — pre-approvals, reimbursements, company cards, and invoices — with each tab appearing only when that record type is turned on.

The Overview separates committed spend, money owed, and money already paid deliberately: these are different things, and a single combined total would be a number that neither describes what anyone owes nor what has been spent. Every metric names the clock it measures (submitted date, decision date, payment date) so figures can be compared consistently. When only one record type is enabled, the overview tab is omitted and that type's breakdown is shown directly.

Use case: A finance manager at a company that uses both a corporate card program and an employee reimbursement policy can now see card spend and reimbursement spend side by side — each on its own tab, each measured consistently — without exporting to a spreadsheet.

Available in: Mango Spend → Analytics