1 Nov 2026 Release

This note covers what shipped after the 18 Oct 2026 Release, through 1 Nov 2026.

A search result opens the record

Choosing a result in search opens the screen for that record. Phone and desktop both do this.

When the list is set to open a details screen, that screen opens on the found record.
When the list has no details screen, a details screen or an update form for that database opens on the record.
When the database has only a list, that list opens with the record selected.
A result that does not belong to a screen in the app stays in search.

The NotionApps site was updated

The public site, the blog, the docs, and the tools that publish them were updated. That work stays on the NotionApps site. It does not change a customer’s app builder.

Every page stays in the docs editor. Hide from navigation keeps that page out of the public sidebar after publish. The page address still opens. This is on staging.

Build an app from a short description

Build with AI is on staging. The walkthrough is Build your first app with the NotionApps Provisioning Tool. It asks for the roles and the first people, then shows a plan. The maker picks an existing Notion page or names a new one. The private app is created in a connected Notion workspace, with a progress bar while it builds.

A written description becomes the screens, records, roles, and workflows. Each named record is its own database. A relation such as Assigned to is one Notion property.
A list shows the empty title saved for that list.
An approver is asked for only when the description includes an approval. That entitlement is turned on before the workflow is created.
A message goes to the person named in the description. Inbox stays open to every in-app channel, so an announcement is not hidden behind messages.
Automation shows on an app that already inherits that entitlement from the account.
A publish failure stays in the build report. Builder Home does not show a sign-in error from this flow.
The first seed person can sign in after their Users row is synced, including when Firebase Admin is not configured. If one invite email fails, the other people are still created.
On an app that already exists, the maker can review the plan and correct the tab labels.
An admin can turn the tool on or off for each subscription plan. A saved choice still applies when the account request fails, including a paid plan turned off and a Free plan turned on.

View as is on staging. It lists people for every login type. Email and a login code are not the only ones.

Choosing a person closes the menu.
The app then shows what that person sees.

Formulas can follow Notion dates

dateBetween can return the difference in whole units, the way Notion does, with the first date minus the second. A formula that calls now() can keep the value synced from Notion instead of being recomputed. Both stay off until formula_notion_dates is turned on. Off, the previous result is unchanged.

Recalculate can count a value it already computed

A rollup or formula can count an input that Recalculate itself computes, including a formula that is not on a fetched screen. Relation fields stay strict. This stays off until recalculate_computed_inputs is turned on. Off, only fetched fields count. On is a superset of off.

Sync can skip a row that has not changed

An hourly Notion file or cover link is saved on its own, so the rest of the row is not rewritten. A list-sync row that has not changed can be skipped. The skip stays off until sync_skip_unchanged_record_writes is turned on.

What makers need to do

Nothing, for search. A published app opens the record from a search result. There is no setting.
Nothing, for formulas, recalculate, and unchanged-row sync, while those switches are off.
Nothing, for the public site. There is nothing to turn on in an app.
Nothing, for an existing docs page. It stays in the navigation.
To hide a docs page, open it in the docs admin, turn on Hide from navigation, and publish. This is on staging.
Nothing, for View as, once it is in production. Open View as and choose a person.
Nothing, for Build with AI, until an admin turns it on for that plan. To build an app, open Build with AI, name the roles and the first people, review the plan, and choose the Notion page. This is on staging.