> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/customize-app/types-of-screens/everyday-chrome-screens.md).

# ✨ Everyday Chrome Screens

Everyday chrome screens are the always-on utility surfaces makers add from **Create New Screen → Everyday chrome**. They give end users a familiar shell — home, search, personal queue, activity, and profile — without building those jobs as ordinary Notion list/detail screens.

{% hint style="info" %}
**Where to find them**\
In the builder, open **Screens → + New Screen**. Under **Everyday chrome**, pick **Home / Today**, **Search**, **My Queue**, **Activity**, or **Profile**. Choose a Notion database as the app context anchor, then click **Done**.
{% endhint %}

![Create New Screen modal showing the Everyday chrome group with all five screen cards](https://iili.io/CwBoqkG.png)

### Screen guide index

| Screen      | Builder card | Primary job                                                       | Best for                                      |
| ----------- | ------------ | ----------------------------------------------------------------- | --------------------------------------------- |
| 🏠 Home     | Home / Today | Today’s next actions, recent activity, one primary CTA            | App landing / “what should I do now?”         |
| 🔎 Search   | Search       | Cross-database keyword search + recent queries                    | Finding records without browsing lists        |
| 📥 My Queue | My Queue     | Personal inbox of work + notifications that need the current user | “What needs me?” across queues and notices    |
| 📜 Activity | Activity     | Timeline of submits, decisions, comments, and updates             | Audit-style feed for operators and makers     |
| 👤 Profile  | Profile      | Default landing screen + notification preferences + logout        | End-user prefs without a custom settings form |

### 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 utility chrome backed by search, activity, and prefs APIs | Give every user Home, Search, Queue, Activity, Profile |

```
Data screens show Notion records.
Automation screens show runtime work.
Everyday chrome screens show the app shell users expect every day.
```

### Shared mental model

Each Everyday chrome screen has three layers:

| Layer                 | What it means                                                   |
| --------------------- | --------------------------------------------------------------- |
| Builder configuration | Empty-state copy, optional Home primary CTA, Search sheet scope |
| Platform APIs         | Cross-sheet search, activity feed, and per-user prefs           |
| Live user experience  | Phone/desktop preview in the builder, then the published app    |

### Shared setup steps

1. Open your app in the builder.
2. Click **Screens** in the left rail.
3. Click **+ New Screen** (bottom of the screen list / config rail).
4. Pick a **Notion Database** as the context anchor (required by the Create New Screen modal).
5. Scroll to **Everyday chrome** and select the card you need.
6. Click **Done**.
7. Customize empty-state title/description (and Home primary CTA when available).
8. Use **Edit Navigation** to place the screen in side nav or tab bar.
9. **Publish** before end users can open it in the live app.

![Example: Home / Today selected in the Everyday chrome picker](https://iili.io/CwBoIBS.png)

### Choosing the right Everyday chrome screen

| User job                                    | Best screen |
| ------------------------------------------- | ----------- |
| Open the app and see what to do next        | 🏠 Home     |
| Find a record by keyword or code            | 🔎 Search   |
| See only work that needs *me*               | 📥 My Queue |
| Review what changed recently                | 📜 Activity |
| Choose landing screen or notification prefs | 👤 Profile  |

{% hint style="success" %}
**Maker tip**\
Start with **Home** + **Profile** for every private app. Add **Search** when users hunt across databases. Add **My Queue** and **Activity** when automation or multi-step work is already in the app.
{% endhint %}

### Safe defaults

* Keep empty-state copy plain-language (“Queue is clear”), not technical (“No activity documents”).
* On Home, set a **Primary CTA** to the main Create Form or Launcher users should open first.
* Put chrome screens in navigation where users expect them (Home first, Profile last).
* Publish after you verify phone and desktop preview for each screen.

### Related docs

* [Types of Screens](https://docs.notionapps.com/customize-app/types-of-screens)
* [Automation Screens](https://docs.notionapps.com/customize-app/types-of-screens/automation-screens)
* [🎨 Polish Your Published App Look and Layout](https://docs.notionapps.com/guides/polish-your-published-app-look-and-layout)