9 Aug 2026 Release
9 Aug 2026 Release
Mixed public + private portals in one app, Content Pages with full HTML/CSS, guided Automation controls so makers can rebuild review hubs and checklists without power-user JSON, richer Decision / Work Queue / Conversation surfaces, app audience & notification prefs, desktop split-view control, and relation-based logged-in user personalization — plus a large reliability pass across public screens, queues, publish, and nested Notion rollups / formulas (support-enabled sync repair).
Earlier updates For logged-in user property filters, email/phone validation, and canvas drag-and-drop reorder, see the 25 Jul 2026 Release. For Board layouts, Details polish, Prefill v2, and Everyday chrome screens, see the 20 Jul 2026 Release and 19 Jul 2026 Release.
What’s new at a glance
Per-screen public access
Keep most of an app private while Welcome, Content, or Create Form screens stay open to guests
Content Pages
Brand landing, consent, and help screens with HTML/CSS — no Notion database required
Guest vs signed-in navigation
Separate “show for guests” and “show when signed in” so public CTAs don’t clutter staff chrome
Guided Workflow / Messaging
Status from/to, role-pool routing, wait topics, Create related records, inbox item type — without JSON
App audience & notification prefs
Tenant (company) + role policy so queues stay isolated; category prefs for Notification Center
Decision writeback + attachments
Map Qualify / Approve / Reject outcomes to Notion statuses; attach files on the decision
Work Queue multi-sheet + tasks
One Needs Review inbox across several asset sheets; tasks from Publish Message
Conversation file uploads
Attach files in conversation replies that travel with the message payload
Automation Launcher announce
Compose and publish announcements from the live launcher; after-action navigation into forms
Desktop split-view toggle
Turn off width-based list/detail split when you want a single-pane desktop layout
See Features below
Relation personalization
Logged-in user property filters can use relation fields (Client / Company)
Nested rollup / formula sync
Support can enable Notion-authoritative repair when nested rollups or formulas show stale or zero values
See Features below
One app, guest door + private workspace.
Content Pages for branded landings.
Guided workflows makers can rebuild.
Queues that respect company and role.
Decisions that write Notion status.
Nested rollups and formulas stay true to Notion.Start here For portals, start with Build a Mixed Public–Private Portal. For review hubs, start with Client Review Hub in 15 Minutes. For photo/doc checklists from a workflow, start with Create Related Checklist from Workflow.
Features
1. Mixed public + private screens in one app
Makers can mark individual screens as public while the rest of the app stays private (OTP). Guests get a guest shell and login CTA; signed-in users keep private queues, lists, and automation screens.
Typical pattern:
Public Welcome (Content Page) + public Submit / Start Intake Create Form
Private My … lists, Work Queue, Decision, Messages after login
One published URL for both audiences
Public Create Forms can also open via ?form= when Public access is on — useful for invite links that stay out of the guest hamburger.
Guide: Build a Mixed Public–Private Portal
2. Content Pages (HTML/CSS, no database)
Content screens are unbound landing surfaces: TipTap / HTML + CSS rendered in a sandboxed iframe (no scripts). Use them for branded welcome pages, consent, help hubs, and CTAs into forms. In-app links navigate inside the app shell without a full reload.
Security note Scripts are not executed in Content Page CSS/HTML. Keep interactive work on Create Forms, buttons, and automation screens.
Guide: Content Page Screens
3. Guest vs signed-in navigation
Public screens expose two navigation toggles:
Show in navigation for guests
Show in navigation when signed in
New public screens default to link-only for guests so Welcome/intake don’t flood the bottom tray. Signed-in landing prefers chrome-visible screens.
4. Guided Automation builder controls
Entitled makers can recreate Client Approval Hub– and Inspection Ops–style flows from the Workflow / Messaging UI:
Status from / to on status-changed triggers
Publish message: channel, topic presets, inbox item type (Task / Decision), role pool or audience routing
Wait with topic wake-ups (and short staging timeouts for demos)
Create related records for photo/doc checklists (not chained Create record steps)
Recipes such as Send to Needs Review and Create photo checklist
Hard rule for makers Route work with role pool / audience — do not pin demo persona emails in live workflow steps.
Guides:
5. App audience & notification preferences
App-level audience policy sets tenant mode (for example a Client relation on the users sheet), role field, and notification categories. Work Queues and Decisions then show the right company/role inbox. Notification Center delivery can honor category preferences (including in-app).
Guide: Configure App Audience and Notification Prefs
6. Decision writeback, review fields, and attachments
Decision screens can:
Map outcomes (Approve / Reject / Request changes / Qualify / …) to Notion Status values
Optionally require a reason
Accept file attachments (not URL-only)
Curate Overview / review fields from the source record (
review_surface)Open an in-place review modal from Work Queue / Approval Inbox patterns
Guide: Decision Screen
7. Work Queue upgrades
Multi-sheet queues (for example Emails + Socials + Projects in one Needs Review inbox)
Tasks created from typed Publish Message events (not only reply waits)
Partners can open source-sheet review forms as secondary screens
Claim / Release / Complete remain the ownership model; completing a queue item is not the same as writing Notion Status — use Decision writeback or an Update Form when status must change
Guide: Work Queue Screen
8. Conversation file uploads
Conversation composers can upload files that travel with message payloads, alongside Decision attachments.
Guide: Conversation Screen
9. Automation Launcher: announce + after-action navigation
Operators can compose and publish announcements from the live Automation Launcher. Launcher actions honor maker OPEN_SCREEN / after-action so intake opens the correct Create Form without demo-only wiring.
Guide: Automation Launcher Screen
10. Desktop list/detail split-view toggle
Appearance includes a control to disable width-based master-detail split. Existing apps keep the current default (split on).
11. Relation fields in logged-in user personalization
Logged-in user property filters can use relation fields (Client, Company, Store relation, and similar), extending the 25 Jul user-property filter story.
Guide: Filter List Screens by Logged-in User Properties
12. Automation product language
In-product copy presents Automation as generally available (not “Beta Testing” framing in the UI). Documentation on this site matches that language.
13. Nested rollup and formula sync (support-enabled)
Some apps show stale or zero values for Notion fields that depend on nested rollups and formulas — for example hours totals built from related session rollups, or a formula that formats another formula (ratio over total). Notion’s property API can return incomplete zeros for those shapes; sync then persisted the wrong number.
This release adds an admin-controlled nested property sync path that re-reads Notion-authoritative values and repairs the app cache:
Off (default) — current production behavior; property-fetch batching fixes still apply globally
Safe — refuse to persist bad nested formula zeros; do not clobber good values with incomplete page-query rollups
Aggressive — safe behaviors plus incompleteness detection for large relations, expanded fulfill dependency chains, and evaluation of simple Notion formula expressions (including formula-over-formula order)
NotionApps Support can enable safe or aggressive for a specific account when nested hours / totals look wrong in the live app but correct in Notion. No maker builder toggle is required.
What makers should do
If a list or details screen shows 0 / empty for a nested rollup or formula that looks correct in Notion, contact Support with the app URL and field names. Do not delete and recreate the Notion properties as a first step — that can break app bindings.
Bug fixes
Public / guest reliability
Guest public-screen loops from
/ext_users401 logout paths are guarded.Public-app preference fetches no longer cause scroll jitter on 401.
Content Page CSS application, double scrollbars, builder screen-switch traps, and in-app link binding are corrected.
Automation queues and decisions
Work Queue / Agency Review blank or wrong multi-sheet Full record mounts are hardened.
Approval Inbox Review white screen from
screenIdrace is fixed.Duplicate Needs Review cards when Publish + Wait run in one workflow are deduped.
Tenant isolation leak in role-pool visibility (clients in different companies sharing queues) is closed.
Work Queue save 403 when Review forms only exist on client-only lists is fixed.
STATUS_CHANGEDon form save so client “With Client” (and similar) status writes reach Needs Review.Decision inbox tenancy when Client relations are ObjectIds is corrected.
Lists, personalization, publish
Related lists emptied by static list sheet-bag ACL are restored.
Multi-hop personalize emptying lists under filter ACL is corrected.
Publish failing on corrupt LIVE versions missing
version_numberis guarded.Signed-in landing no longer prefers non-chrome-visible screens.
Workflow REFERENCE coerce for single values; conversation “You” labels for View As / end-users.
Nested data sync
Nested rollup / formula zeros from incomplete Notion property responses are no longer trusted when Support enables safe or aggressive nested property sync.
Formula-over-formula resolution order is fixed so dependent formulas (for example a ratio that references a total formula) evaluate after their formula dependencies, not only after leaf rollups.
Conversation composer
File drop / attach no longer crowds the reply field.
Attachment links in message bubbles use readable contrast.
Entitlement / publish gating
Ordinary apps with Workflow subscription entitlement no longer hit false-positive approval publish gates based on form-name heuristics.
Messaging entitlement resolves via the subscription-aware path.
Documentation for this release
Recommended learning path
Re-test Decision writeback + Work Queue claim/complete after Publish
For Jul 25 filter/validation/canvas items, continue with the 25 Jul 2026 Release
Availability notes
Per-screen public access / Content Pages / dual nav: available to entitled makers; test guest + signed-in paths after Publish
Guided Workflow / Messaging controls, audience policy, Decision writeback, multi-sheet Work Queue, Conversation files, Launcher announce: require Automation / Workflow / Messaging entitlements for the account
Desktop split-view toggle: Appearance; existing apps keep prior default
Relation personalization: Pro+ logged-in user property filters (same plan bar as 25 Jul) plus relation field support
Nested rollup / formula sync: default off; Support enables safe or aggressive per account when nested values are wrong in-app
Reliability fixes: no new maker configuration — Publish / hard refresh as usual