What is shared and what differs
| Surface | Product behavior |
|---|---|
| Browser | Full authenticated workspace and specialist configuration |
| Native iOS/Android | Permission-scoped daily work, selected native workflows, bounded offline evidence and explicit web handoffs |
| Desktop macOS/Windows shell | Full hosted workspace with native lifecycle, notification and file/download controls; internet required |
| Guest native check-in | Separate account-free device setup/admission path with its own device credential; no workforce access |
All surfaces retain current workplace/source permissions. An installed application or successful sign-in does not grant membership, employment or module access. A native home being implemented does not establish that every detail action is native or accepted on a physical device.
Native offscreen pause: retained Assistant and Automation screens pause renewing content when unfocused or when the app is backgrounded. Bookings day/table-plan and Phone query timestamps stop advancing offscreen and refresh on return. A rapid background/foreground or blur/focus transition retires its old read lifetime; unsent same-source forms remain mounted. Unit/source verification does not establish installed-device acceptance or app-store publication. A screen nobody touches for five minutes also stops renewing private content until the next use; see the native idle pause.
Workforce navigation and native capability coverage
Navigation has five destinations: Home, Browse, a personal middle shortcut (initially My Work), Messaging and Profile. This supersedes the earlier four-tab Today/Messages/My Work/More composition. Installed-device acceptance is pending. Phones show the destinations in a bottom bar. Tablet rail, iOS build 17 and Android build 22 or later: windows at least 768pt wide (iPad and Android tablets) show them in a slim labelled rail on the left, each label under its icon, instead of the earlier drawer-width sidebar. At large text sizes each label shrinks to fit its slot on one line. Tablet rail evidence The header workplace selector changes the current authorized context. It explains that the list contains workplaces for the current signed-in account. Add a workplace opens that authorised list, Refresh workplaces, and an optional Soupy invitation-link field. Reviewing a link opens the existing acceptance screen; it grants nothing automatically. Administrators must invite that same email, and a connection is required to refresh or review an invitation. It does not keep multiple logins signed in. Browse shows every admitted native area with meaningful work-area artwork, plus explicit web tools, subject to installed support, source authority and server feature pauses. Search, Notifications, Support and Pending work retain their cross-cutting controls.
In Profile → Your middle button, each person chooses an available module or My Work. The preference is saved per account/workplace on this device; web-only choices say Opens web workspace. If authority or installed support changes, the button falls back to My Work until the choice becomes available again. Changing the shortcut grants no access. Profile also retains appearance preferences and app update information; applying an update uses the existing safe Profile workflow.
Profile groups icon-labelled, explained links under Your work and App and preferences. Notification preferences contains Enable work notifications, alongside the existing workplace quiet-hours and delivery preferences. Permission is requested only after that explicit tap; loading Profile or Notifications does not request it. Device access remains a separate security section in Profile with its existing revoke confirmation. Annotation repair evidence separates source/render checks from store and installed-device availability.
Shell header (20 November 2026 restyle, iOS build 17 and Android build 22 or later): tab headers no longer repeat a Profile button, since Profile is a tab. Profile's header adds a Support and account requests icon; the Profile list keeps the same link. Home's header adds the notifications bell beside the workplace switcher (notification tray). Messaging's New direct message moves from a floating button to an icon beside the Messages title. It still appears only to people who can view direct messages and is disabled offline. Dark mode uses graphite surfaces; times and due labels use a monospaced face.
Bookings and Inbox (21 November 2026 restyle, iOS build 17 and Android build 22 or later): Bookings' New reservation or walk-in becomes a floating button, still disabled offline, and its status bars take status colours. Live table plan, Private events and Published menus become buttons. Booking detail leads with status and Accessibility needs stamps, then date, time and guest count tiles and labelled Site, phone and email rows. New booking starts with a Reservation/Walk-in switch, replacing the toggle in the guest card. Site, area, table, start-time and allocation choices across Bookings are chips; a start-time chip shows the start and how many allocations are free. Inbox rows show an unread dot, guest, time, subject and preview. A conversation shows guest messages on the left and team replies on the right; its assign, mark-read and close commands share a row. Permissions, offline rules and every command are unchanged.
Ticketing and Guest context (21 November 2026 restyle, iOS build 17 and Android build 22 or later): Ticketing home opens with a graphite Next doors card for the soonest live Event on the loaded page, with Start door and Event orders when the person may use them; it hides while searching. Orders and Passes sit beneath it, and Events become cards with a status stamp, date and start time. Admissions is graphite in both appearances, header and status bar included. It shows admitted, still-to-come and (for door administrators) offline-conflict counts, chooses the check-in list with chips and keeps the camera viewfinder in place. The latest result shows as a green Admitted, amber Already admitted or blue Admission reversed panel. Each guest row has an inline Admit button or an Admitted stamp, with Review check-in correction as a link for administrators. Order service shows the purchaser with a status stamp, total and ticket count, ticket rows with status stamps and Resend tickets beside the Tickets heading, which still opens the send review. Guest context shows initials, lifetime spend and order count when the person may see business history, contact and tag rows, and activity with dates. Native Ticketing still has no Event detail, ticket-type sales switches or customer directory; those remain on the web. Permissions, offline rules and every command are unchanged.
Tasks, Rotas, Clocking, People and Knowledge (21 November 2026 restyle, iOS build 17 and Android build 22 or later): A ticked task or checklist item fills with ink and a contrasting tick and is struck through. Task detail opens with a status stamp and summary; the checklist count and bar sit above the items, and the evidence photo and file commands are square icon buttons beside each item that needs them. Complete task stays last and stays disabled until required items are done. A shift brief leads with a Shift brief · vn stamp and a bulleted list, then its checklist and acknowledgement. The My rota calendar marks shift days with a dot and fills the chosen day. Shift and offer cards show the date, the hours in large monospace, then role, Site, space, break and assignment state on one line; the pay estimate follows the shift list. Clocking shows the current time in large monospace above the status, and NFC scanning is a round button. A Person profile shows initials, job title and work email, employment rows on one's own record, assignment rows and contract rows with status stamps. Knowledge marks training Required or Completed at the row end and lists documents with a file icon and version. Native rotas still show only the person's own shifts, with no who's-on list or swap; Clocking has no next-shift card; People has no call or message actions. Permissions, offline rules and every command are unchanged.
Maintenance, Stock count, Purchase approval, Assistant and Profile (21 November 2026 restyle, iOS build 17 and Android build 22 or later): Maintenance shows open faults as cards with status, Needs approval, urgent and high priority stamps, the reported date, the fault title, Site, asset, assignee and reporter, and any requested spend; Report a fault becomes a floating button for people who may report. Report a fault picks the building and every priority, risk or condition value with chips across venue-operation forms; photos are added from two dashed Take photo and Choose photos tiles, each selected photo has retry and remove icons, and Area secured is a checkbox. Stock count shows how many lines are counted with a bar, a Find a product search when a count has more than five lines, and − and + buttons beside each product's count field; − on a blank line records zero, and the expected quantity and variance show only when the person may see them. Purchase approval leads with an Awaiting your approval stamp, the order number and supplier, then total and net tiles and the lines with their totals; a decision reason is still required. Assistant questions sit on the right in ink and answers on the left on a card, suggested questions are chips, and a proposal card leads with its state stamp and version. Profile opens with initials, the person's name and workplace; Your work rows have icons, Pending actions shows its count, and Appearance is a single segmented control. Purchase approval has no Send back or Edit lines, and Assistant has no voice input; those were drawn in the canvas without a mobile source. Permissions, offline rules and every command are unchanged.
Loyalty, Lost & Found, Automation, Assets, Production and EPOS (21 November 2026 restyle, iOS build 17 and Android build 22 or later): Loyalty groups Fulfil a reward and Member service in captioned cards; the claim reference is monospace and member results show initials. Lost & Found leads with the strongest suggested match as a Possible match card with its score, report reference and Review match; other matches and found property follow, each found item with an icon and status stamp, and Record found property is a floating button for people who may manage items. Automation switches between Approvals and Runs, each with its count. An approval is a card with an Awaiting approval stamp, its version, action, scope and requester; Review opens the summary, the rejection reason and Approve or Reject as before. Runs shows today's, succeeded and failed counts for the loaded runs, then each run's status, time, trigger, outcome and attempts; people who cannot approve see only runs. Assets leads with a Scan an asset tag card. Its Needs attention and Checked out tiles filter the list, as do chips for All, Needs attention, Checked out and the three most common categories; Checked out now also counts overdue and handover-pending equipment. Asset rows show the serial number in monospace and one stamp: Out, Overdue or Handover while away, otherwise OK, Attention, Fault or Retired, or Fixed for working fixed equipment; the row text keeps the full status. Production shows exceptions as bordered cards and recipes with an icon and Record batch. EPOS intelligence switches between Work (recommendations, Active or All) and Evidence (recent trading records with monospace net totals); an evidence link opens Evidence. Rule lists and switches, inspections due, today's batches, allergens, labels, bills linked to bookings, EPOS connection status and product mapping were drawn in the canvas without a mobile source and are left out; rules stay on web. Permissions, offline rules and every command are unchanged.
Talent and Phone (21 November 2026 restyle, iOS build 17 and Android build 22 or later): Talent performance rows lead with the start time in monospace and end with the engagement state as a stamp; a reported completion shows as a link-coloured line, and Invoice service and Talent planning carry icons. A performance opens with a card holding its state (and Retained commitment when only that remains), the act, the time in monospace, Fee and Payee, then the terms, act report and completion flow as before. Phone opens with a receptionist card: its name, a Ready or Not ready stamp, the active number in monospace, the readiness sentence and the web workspace note. Calls and Callbacks share a full-width switch. Each call row has a round phone icon, warning-coloured while a callback is owed, the time (today) or date, and a Callback or status stamp. Call details open with a card of stamps, caller, start time and summary, then transfer and callback state; the timeline is one card. Talent's roster, discovery and money tabs, Message act, Confirm arrival, Phone routing switches, bookings-taken counts and a dial-back link were drawn in the canvas without a mobile source and are left out. Sport, Displays, Guest Wi-Fi and Studio, also in that canvas row, have no native screen and stay in the web workspace. Permissions, offline rules and every command are unchanged.
Channel thread (21 November 2026 restyle, iOS build 17 and Android build 22 or later): the conversation header shows the channel in the heading face over its member count and workplace, with a hairline below. Day dividers are a centred monospace label (Today or the date), message times are monospace, and a reply count reads as a link ending in an arrow. A message linked to a record shows it as a chip. The composer is a flat bar with Message options, the message field and Send message. Assistant conversations share the header. The canvas has no inline reaction, mention or reply controls, but they stay on each message alongside the ⋯ actions. Permissions, offline rules and every command are unchanged.
The daily-work and Messages surfaces preserve native text scaling. Changing iOS text size refreshes text measurement without reopening the screen or resetting an editor's draft. Bottom destinations have explicit spoken names; their decorative icon glyphs do not form part of those names.
Home adds a labelled completion ring for the loaded tasks due today, prioritizes unfinished tasks and charts loaded team attention by work area. The ring, the Today's tasks list and All tasks and checklists share one card; the shift card shows the countdown or date beside its stamp. Bookings adds labelled status bars for its current day/site. These are bounded source views, not whole-business totals or invented historical trends. Browse uses existing module artwork; loaded empty screens retain their quiet icon treatment. Rendered comparisons and acceptance limits cover both themes at phone/tablet browser sizes.
Home loading: the task completion card and Team today heading stay in place while their first reads load. Unknown task counts show dashes and loading text; a missing offline task snapshot asks for a connection instead of reporting no work. No shift scheduled appears only once both eligible rota and clocking reads have finished. Current source permissions and saved-view expiry still decide what can be displayed.
The supported native home list includes Today, Messages, Tasks, Knowledge, Rotas, Attendance, People, Maintenance, Assets, Lost Property, Ticketing, Bookings, Inbox, CRM, Loyalty, Talent, Purchasing, Stock, Production, EPOS, Assistant and Automation. Portfolio and specialist planning/configuration retain web handoffs. Native rota exchange is explicitly unavailable; the personal schedule remains separate from web management and exchange authority.
Native detail routes include task creation/management/checklists; Knowledge content; personal rota history/brief; attendance/missed-punch review; People profiles; fault reporting; asset scanning/detail; Lost Property item/match/report; Ticketing Orders/Passes/door recovery; Booking creation/detail/table plan/menus/ preorders/private events; Inbox conversations/forms/Booking proposals; Loyalty members; Talent engagements/money; Purchasing approvals/receipts; Stock lot/count/ create/transfer; Production batches; EPOS detail; and Assistant conversations. Each route still checks its source authority and implementation-specific limits.
Native lists that span Sites open on All sites, as on the web: People (Directory site), Attendance review (Attendance site), Private events (Event site) and Bookings; Stock opens on All accessible places for a business-wide reader or anyone reading two or more places, and Team Tasks on All places (Whole workplace for business managers). Each row still passes its own Site's check. A chosen Site lasts for the workplace until it changes or the Site leaves your access; with one Site the screen shows that Site. Published menus list every published menu without a Site choice. Steps that need one Site ask for it: Attendance manager work reconciliation asks which Site, Stock asks for a place before counts, transfers and waste unless you hold them business-wide, and task assignment keeps a place picker. A place manager's All tasks list is view-only, without assignee names.
The native private-file guard covers Messages, Maintenance, Lost Property photos, Task Notes, Inbox attachments and Purchasing receipt originals. A loading file stops on account/session, workplace, screen, connection or source loss before being written to temporary storage or opened for sharing. The temporary copy is deleted when sharing finishes or a pending share is retired. Once the device share sheet has opened, Soupy cannot withdraw it. Installed-device acceptance remains separate from the local component checks.
Native workspace search
Unreleased until the next native update. Home's header has a Search workplace icon beside the workplace switcher. Search reads the same signed-in, server-checked search as the web header (Workspace search) over the app's ordinary connection. The server returns only records and destinations the person may open in the selected workplace; the app adds no permission rules of its own.
Typing two or more characters searches after a short pause. All shows up to eight results per category. A category chip narrows the list and pages it with Previous matches and Next matches. The Results count describes returned results, with + when more exist; a limited scan says so instead of reporting no matches. Each row shows the owning area's icon, the record, its area and page, and identifying details. A customer best match adds its permitted facts.
Opening a result checks access again first. It needs the displayed search's current access lease, renewed about every two seconds while Search is open, and a link inside the selected workplace. It then opens the matching native screen when that area is available in the app, the area's web screen when it is paused or web-only, and otherwise the exact web page, where the browser checks access. A result in another workplace never opens. Search needs a connection: offline it sends nothing and says so. Changing workplace clears the phrase and results.
Search is a rollout feature. When the deployment pauses search, the Home icon
disappears and a direct /search link shows Temporarily unavailable;
installed apps learn of that pause only from the matching backend deployment.
Search was hidden on native from 17 September 2026 to keep the first pilot to
six areas. Filly re-admitted it on 21 November 2026 on this permission-checked
read path, replacing the older screen's cached query.
Not on native: Recent (web keeps typed references in browser storage), Jump to (Browse lists every available area), customer shortcut links, Keep looking handoffs, keyboard shortcuts, per-area accent colours and a separate record-reference column, because results carry references only inside their details.
Offline work and uncertain commands
The workforce app reads current device network status at startup and whenever it returns to the foreground, as well as listening for connection changes. A missed background callback can then recover without restarting the app. Network availability still requires separate server-confirmed authentication before online work resumes. Saved drafts and offline evidence are preserved. Builds without this check, such as Play build 17, can remain on Saved view after a normal resume. Installed-device acceptance of this check remains outstanding.
Encrypted local storage is partitioned by environment, installation, principal and workplace. A server-issued offline lease is bounded to twenty-four hours. Downloaded eligible Tasks/checklists may complete offline; attendance observations retain captured evidence and require later review. Reconnection reauthorizes commands and checks source revisions before applying them.
Native My Work and Home save freshly authorized attention projections in the encrypted workplace cache. Saved view remains available offline within the existing workforce lease; first download still requires a connection. A received refusal retires that saved queue. Older mixed-source cache entries are not reused. Only eligible downloaded Tasks/checklists support offline completion; other work cards wait for a connection. Removed rows cannot publish late navigation errors. Open training, Talent completion, delivery receiving and EPOS recommendation drafts survive a temporary disconnect but require fresh authority for submission. Receiving photos/private dockets and late command acknowledgements retain their current source receipt; a stalled read does not authorize a new operation.
Approvals, external sends, booking allocation, financial effects, stock posting, custody and redemption require a connection. Message drafts are never sent merely because the device reconnects. A lost online receipt retains the exact operation for recovery instead of inventing a replacement action.
Pending work exposes saved drafts, observations and uncertain/conflicted work. Sign-out considers retained evidence across workplaces so it cannot be submitted under the next person's account. Expired/revoked access preserves evidence for recovery without granting operational access. Explicit discard is separate and can be irreversible. Ticketing door evidence has its own reconciliation/purge protocol and cannot be erased through ordinary queue discard.
Camera/photo/file attachments support permitted report and message workflows. Capture/upload progress, protected source context and installed-device acceptance remain separate from a saved draft or server implementation.
Native updates and availability
Profile distinguishes installed binary version/build from the running downloaded update identity/date. A compatible update can be checked, downloaded and applied by an explicit restart. Downloaded does not mean currently active. Edits, uploads, synchronization and uncertain commands hold restart until safe; retained drafts are flushed without deletion. Native binary changes need a matching signed/store build rather than a JavaScript update alone.
iOS build 17 or later and Android build 22 or later receive JavaScript updates, so they run the app described here once the latest update is applied. Earlier builds (iOS 16, Android 21 and before) use an older native runtime, so current updates do not reach them; they need a newer build. Work that has not yet reached installed apps says so where it is described.
Before restarting, the app pauses background content-read renewals and gives already-started requests up to five seconds to settle before checking saved work. A request that remains unfinished still blocks restart; account/workplace changes cancel it. Failed preparation resumes reads with fresh authorization. Saved drafts, queued evidence and sign-in remain intact. Publishing an update does not prove it activated on an installed phone.
The checked-in public download manifest at this handbook baseline exposes no
public desktop installer. /download labels mobile as in testing and states that
public App Store/Google Play downloads are not available. Internal APKs, signing,
provider setup and private beta acceptance have separate evidence/runbooks.
Update these statements with the public manifest/store evidence when publication
changes; do not infer public availability from a successful build.
Links that open the app
Production links configured 17 November 2026; signed-device checks pending.
Staff links on soupy.ai open the installed Soupy app instead of the browser:
workplace access invitations (/accept-access/…), clocking links (/clock/…),
asset scans (/assets/scan/…) and app links (/app/…). This covers the
production app from the App Store, TestFlight, Google Play or an internal Soupy
Android build. Without the app, the same link opens the web page. Customer
pages such as checkout, forms, document signing and Wallet passes always stay
on the web.
A clocking link opened in a browser shows Open Soupy. Opening the page or the app does not record attendance; the app still requires sign-in and clocking permission. A phone that installed Soupy before links were configured may keep opening the browser until the app updates or the phone rechecks its links.
Installed desktop behavior
Desktop uses the hosted workspace, including its work-area navigation, settings and source commands. External provider journeys open in the system browser; return links select a destination without granting business authority. The native bridge is limited to approved operations and does not expose arbitrary files or shell commands to hosted pages.
Desktop guards unsaved edits, pending commands and retained evidence before close, reload, update, account change or sign-out. A successful earlier save does not mark text typed afterward as saved. A provider handoff, browser approval or first sign-in is separate from accepted retained-session startup. Beta/stable channels and staging/production identities remain separate; settings must not silently move a stable installation onto beta.