Product Update - September 11, 2026

Sites Authoring Redesign — Guided site creation, scheduled publishing, and a cleaner editor

Creating and publishing internal sites is now a guided, decision-aware experience. A new three-step composer walks authors through picking a starter template, naming the site, and setting its audience — replacing the previous empty-drawer-to-blank-page workflow that left authors with nothing to do. A starter gallery covers common use cases (department hubs, policy portals, onboarding sites, and more) so teams can start from something real instead of from scratch.

Publishing a page now opens a focused sheet rather than a one-line browser confirm. Authors choose the audience, set a publish date and time if they want to schedule ahead, and decide whether to notify followers — all from one panel. The AI assistant panel in the editor collapses when not in use, returning the full canvas width to the page you're building.

Use case: A communications manager creates a new "Field Ops Playbook" site by picking the Department Hub starter, names it in step one, restricts it to field managers in step two, and schedules its publish for next Monday morning — without leaving the composer.

Available in: Sites → Site Gallery → New Site; Sites → Page Editor → Publish

---

Ask AI in External Hubs — Embed the workforce AI assistant in your Hub with one code snippet

Organizations that run an external Hub now have a direct path to bring the MangoApps AI assistant into it. An admin enables Hub embedding in Ask AI settings, copies the generated snippet, and pastes it into the Hub's Code Embed block. Hub users then get a full AI assistant panel — same grounded, permission-aware answers, same agent capabilities — without navigating to a separate app.

The embed is scoped to the tenant and secured with a rotating key that admins control. Accepted and rejected origins are logged rather than silently dropped, and the session is isolated from the employee's main Workforce tab so conversation state stays clean.

Use case: An IT admin adds the Ask AI assistant to the company's Hub so warehouse employees can ask shift, policy, and training questions directly from the dashboard they already open every day.

Available in: Ask AI → Admin Settings → Hub Embedding

---

App Builder: App Lifecycle & Live App Packs — Formal publish/unpublish/retire flow and capacity-based billing for custom apps

Apps built with App Builder now move through a clear lifecycle: unpublished (visible only to creators and app admins), live (deployed to users), and retired (taken offline without deletion). Admins publish and unpublish apps explicitly, which means no app reaches employees without a deliberate decision. An unpublished sandbox cap keeps draft apps from accumulating without review.

Billing shifts from per-use charges to capacity packs: organizations purchase a pack of 3, 10, 25, or 100 live app slots, and publishing is gated at that count. The live-app register shows current usage against pack capacity, and self-serve purchase is available when a team needs to grow. Mini apps from the catalog count toward the same pack, simplifying the number of line items to track.

Use case: An operations team builds and tests a field inspection app while it is unpublished, then an admin publishes it to the field crew. During a form update the admin unpublishes it temporarily, keeping the roster from submitting until the new version is live.

Available in: App Builder → My Apps → Publish / Unpublish / Retire; Admin → App Builder Settings → Capacity