Product Update - August 21, 2026

Product Update — August 21, 2026

---

Mango Spend: Company Card Receipts Now Count Against Pre-Approvals — corporate card spend tracking inside pre-approval budgets

Employees and managers who put approved purchases on a corporate card can now attach those card receipts directly to the pre-approval that authorized the spend. The pre-approval's budget bar, overage alerts, and close-out summary now account for both out-of-pocket expense reports and company card receipts in a single total — so approvers see an accurate, real-time picture of what has actually been spent against any authorization.

Previously, card-based spending existed as a separate paper trail; teams had to manually reconcile the two and the approval record never reflected the true actuals until the expense report came in. This closes that gap for any business that routes some purchases through corporate cards and others through employee reimbursement.

Use case: A manager pre-approves a $3,000 team offsite. Two hotel rooms are paid on the company card and submitted as card receipts; meals are reimbursed via expense report. Both flows now count toward the same $3,000 pre-approval budget, and the manager sees a single remaining-balance figure rather than two disconnected numbers.

Available in: Mango Spend → Pre-Approvals → Pre-Approval Detail

---

Recognition Award Cycle Nominations API — nominate employees for award cycles from mobile and third-party apps

A new REST API lets mobile apps and integrations fetch open award campaigns and submit employee nominations programmatically, using the same eligibility rules, cycle status checks, anonymity policy, and confirmation messages as the web interface. The API also surfaces open campaigns in the lite app-listing endpoint, so clients can discover which nomination windows are currently active without a separate call.

The nomination endpoint mirrors the web form precisely: a caller cannot nominate someone already nominated for the same award, cannot nominate themselves, and cannot reach a cycle the UI would refuse — the same eligibility gates run on both paths. This makes the award nomination experience consistent across the browser, the native mobile app, and any third-party HR tooling connected through the API.

Use case: A field-service company whose employees primarily use the mobile app can now surface an open "Employee of the Month" campaign and collect nominations without requiring workers to log in on a desktop browser.

Available in: Recognition → Award Cycles → Nominate (API: POST /api/v1/recognitions/cycle_nominations)

---

SAML SSO for Desktop and Mobile Native Apps — single sign-on with SAML providers works end-to-end in the native apps

Employees at organizations using SAML-based identity providers (Okta, Azure AD, PingFederate, and others) can now complete the full SSO sign-in flow inside the MangoApps desktop and mobile native apps without being redirected to a browser session. The platform mints a server-side one-time code at the end of the SAML assertion flow and delivers it to the app via a deep link, so the native app receives an authenticated session without needing to handle the SAML assertion itself.

Previously, SAML-authenticated users who tried to sign in to the native app would initiate the SSO flow, be authenticated in the browser, and then find themselves stuck — the app's session was never established and the client timed out after three minutes. Employees at SAML-only organizations had no path to using the desktop or mobile app.

Use case: An IT administrator who has configured Okta as the company's identity provider can now tell employees to sign in to the MangoApps desktop app with their company credentials — the Okta login page appears, the employee authenticates, and the desktop app opens in their session automatically.

Available in: Administration → Security → SSO / SAML Configuration