19 Jul 2026 Release
New Everyday chrome screens, published-app look and layout options, and a clearer history experience in the builder.
What’s new at a glance
Section titled “What’s new at a glance”| Capability | What you can do | Learn more |
|---|---|---|
| Everyday chrome screens | Add Home, Search, My Queue, Activity, and Profile as first-class app screens | Everyday Chrome Screens |
| Published app look & layout | Layout density presets, login polish, desktop master–detail, sticky actions | Polish Your Published App Look and Layout |
| History panels | Recovery History and Version History open expanded by default | Recovery History · Revert Version History |
Data screens show Notion records.Automation screens show runtime work.Everyday chrome screens give every app a familiar home, search, queue, activity, and profile shell.1. Everyday chrome screens
Section titled “1. Everyday chrome screens”Everyday chrome screens are utility screens you add from Create New Screen → Everyday chrome. They give end users a familiar shell — home, search, personal queue, activity, and profile — without rebuilding those experiences as ordinary Notion list or detail screens.
Screen index
Section titled “Screen index”| Screen | Builder card | Primary job | Best for | Docs |
|---|---|---|---|---|
| 🏠 Home | Home / Today | Today’s next actions, recent activity, one primary CTA | App landing / “what should I do now?” | Home |
| 🔎 Search | Search | Cross-database keyword search + recent queries | Finding records without browsing lists | Search |
| 📥 My Queue | My Queue | Personal inbox of work + notifications for the current user | “What needs me?” across queues and notices | My Queue |
| 📜 Activity | Activity | Timeline of submits, decisions, comments, and updates | A shared feed of what changed in the app | Activity |
| 👤 Profile | Profile | Default landing screen, notification prefs, logout | End-user prefs without a custom settings form | Profile |
How Everyday chrome differs from other screen families
Section titled “How Everyday chrome differs from other screen families”| Family | What it shows | When to use it |
|---|---|---|
| Data screens | Notion rows (lists, details, forms) | Browse, create, or edit records |
| Automation screens | Workflow / messaging runtime work | Claim work, decide, converse, recover failures |
| Everyday chrome | App-wide home, search, queue, activity, and profile | Give every user a familiar app shell |
Hub docs: Everyday Chrome Screens · Types of Screens · Automation Screens
Shared setup steps
Section titled “Shared setup steps”- Open your app in the builder.
- Click Screens in the left rail.
- Click + New Screen.
- Pick a Notion Database as the context anchor.
- Under Everyday chrome, select the card you need.
- Click Done.
- Customize empty-state copy (and Home’s primary CTA when available).
- Use Edit Navigation to place the screen in side nav or tab bar.
- Publish before end users can open it in the live app.
Which chrome screens need Automation
Section titled “Which chrome screens need Automation”Not every Everyday chrome screen requires Workflow, Messaging, or Approvals.
| Always available | Requires Automation |
|---|---|
| Home, Search, Profile | My Queue, Activity |
When Workflow, Messaging, or Approval Management is not enabled for the app, My Queue and Activity appear in a locked Queue & activity group in the Create New Screen picker.
Per-screen highlights
Section titled “Per-screen highlights”🏠 Home
- Landing surface for “what should I do next?”
- Optional Primary CTA pointing at a Create Form or Automation Launcher
- Recent activity summary when the activity feed has items
- Configurable empty-state title, description, and action label
Docs: Home
🔎 Search
- Cross-database keyword search against linked Notion data
- Recent query history in the end-user experience
- Available in builder preview and in published apps
Docs: Search
📥 My Queue
- Personal inbox across approvals, work items, and notifications for the current user
- Available when Automation is enabled for the app
- Empty state when the queue is clear
Docs: My Queue
📜 Activity
- Timeline of submits, decisions, comments, and field updates
- Available when Automation is enabled for the app
- Useful for operators and makers who need a shared view of recent changes
Docs: Activity
👤 Profile
- Choose the default landing screen for the signed-in user
- In-app / email notification preferences
- Logout from the published app
Docs: Profile
Builder preview
Section titled “Builder preview”After you add a chrome screen, phone and desktop preview show the empty state or content right away. Home’s primary CTA opens the target screen’s layout (for example Create Form or Launcher), and chrome tabs keep clear titles such as Home and Search.
2. Published app look and layout
Section titled “2. Published app look and layout”Make published NotionApps feel like finished products — with clearer login, denser or airier layouts, and better desktop list/detail behavior.
Guide: Polish Your Published App Look and Layout
What you get
Section titled “What you get”| Feature | Where you configure it | What end users see |
|---|---|---|
| Login hero + wrapping title | Automatic from app color / icon / name | Brand-colored header, rounded inputs, full app title |
| Layout presets (Compact / Comfortable / Showcase) | Settings → General → Layout presets | Spacing, type scale, and denser or airier forms & lists |
| Color presets | Same General appearance preview (or Appearance) | Accent / theme color |
| Sticky desktop Submit | Create/Update Form Behaviour (or defaults) | Submit stays pinned while scrolling on desktop |
| Heading section rhythm | Add Heading components on forms | Clear visual groups between field sections |
| Desktop master–detail | Automatic on wide desktop List screens | List left · details/forms right |
| Details sticky actions | Automatic on desktop Details | Edit / Delete stay visible |
| Page Content table of contents | Show Page Content settings | Side TOC can appear when enough headings exist |
| Cleaner cloned app names | Publish + login display | “Copy of” prefixes removed for end users |
Layout presets
Section titled “Layout presets”| Preset | Character | Best for |
|---|---|---|
| Compact | Tighter rows and padding, smaller type | Dense operational apps |
| Comfortable | Default; taller fields, softer radii | Everyday work apps |
| Showcase | Larger type, airier spacing | Portals and catalogues |
Related: Desktop View · Customize App
3. History panels expand by default
Section titled “3. History panels expand by default”Recovery History
Section titled “Recovery History”Recovery History (under Databases tools) now opens expanded on first load so you can see available rollback snapshots without an extra click.
Docs: Recovery History
Version History
Section titled “Version History”Version History (under Settings) now opens expanded on first load so prior app versions and revert actions are visible immediately.
Docs: Revert Version History
4. Documentation for this release
Section titled “4. Documentation for this release”Everyday chrome
Section titled “Everyday chrome”| Doc | Link |
|---|---|
| Everyday Chrome Screens (hub) | Open |
| Home | Open |
| Search | Open |
| My Queue | Open |
| Activity | Open |
| Profile | Open |
Guides & basics
Section titled “Guides & basics”| Doc | Link |
|---|---|
| Polish Your Published App Look and Layout | Open |
| Recovery History | Open |
| Revert Version History | Open |
Recommended learning path
Section titled “Recommended learning path”- Everyday Chrome Screens
- Home + Profile
- Polish Your Published App Look and Layout
- If you use Automation: add My Queue / Activity, then return to the Automation hub
Availability notes
Section titled “Availability notes”- Everyday chrome — Home / Search / Profile: available whenever you can add screens in the builder
- Everyday chrome — My Queue / Activity: require Workflow, Messaging, or Approval Management
- Layout presets & published look: available in Settings and published apps; existing apps keep prior spacing until a preset is chosen
- Recovery History / Version History expand-by-default: builder preference only; restore and revert access are unchanged