Product Update - May 20, 2026

Safety Hub Mobile API — Safety incident feed and scoreboard for mobile and headless clients

Safety Hub now exposes two new read-only JSON API endpoints designed for native mobile apps and third-party integrations. The first returns an employee's personal feed of submitted incidents and safety observations — date-sorted and enriched with UI-ready metadata like severity labels, status colors, and deep links. The second provides a team-level analytics scoreboard (TRIR, DART, compliance score, breakdowns by type/severity/status) gated to managers, mirroring the existing web analytics dashboard. Both endpoints respect per-module toggles and anonymous submission settings, so the API surface reflects the same rules as the web experience.

Use case: A field safety manager on a manufacturing floor opens the company's mobile app to check their team's incident scoreboard for the week — without needing to log into a desktop browser.

Available in: Safety Hub → API → Submitted By Me / Scoreboard

---

Calendar Default View & Session Persistence — Admin-configurable calendar starting view with per-user memory

Admins can now configure separate default calendar views for desktop and mobile devices — choosing from Month, Week, Day, or Agenda — so employees land on the most relevant layout for their context without any manual adjustment. Beyond the admin default, the calendar also remembers each user's last manually selected view across sessions: switching to Day view on Tuesday means the calendar opens in Day view on Wednesday. This preference is stored locally and silently falls back to the admin default in private browsing mode or when storage is unavailable.

Use case: A logistics team primarily works on a weekly schedule review; the admin sets the default desktop view to Week, so every team member lands there on first load without any configuration on their end.

Available in: Calendar → My Calendar → View Settings

---

Contracts: Multi-Location Scoping & Payment Structure — Location-based contract visibility and payment type categorization

The Contracts app now supports assigning a single contract to multiple locations, enabling location-based filtering and row-level visibility so employees only see contracts relevant to their site. A new payment structure field lets teams categorize contracts by payment arrangement (such as fixed-fee, time-and-materials, or milestone-based), making it easier to filter and report across a contract portfolio. Community-level scoping further refines who can view a contract, complementing the existing business-level controls.

Use case: A facilities manager at a company with offices in three cities assigns a vendor contract to all three locations — each site's team can find and filter it locally, while the central procurement team retains full visibility across all sites.

Available in: Contracts → Contract Details → Locations / Payment Structure