> 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.md).

# Types of Screens

### Types of Screens

#### Types of Screens

Screens are the pages your app users open to view data, update records, submit forms, make decisions, follow workflow status, send messages, recover workflow problems, or act on work routed by automation. A good screen type choice keeps the app simple: users should immediately understand what they are looking at, what they can do, and what result to expect after they act.

NotionApps screen types fall into three families:

* **Data screens** show or edit records from connected Notion databases. These are the standard screens used for lists, detail pages, update forms, and add-item forms.
* **Automation screens** show work created by workflows, approvals, messages, notifications, exceptions, launch actions, linked app exchanges, and operational runtime data.
* **Everyday chrome screens** give users Home, Search, My Queue, Activity, and Profile — always-on app-shell utilities backed by search, activity, and preference APIs rather than a single Notion list or automation inbox.

![Work Queue screen in the NotionApps builder.](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2F5nB1Ti9ZiYZNqMNf7vU3%2Fautomation-screen-work-queue-builder-20260705.png?alt=media\&token=cbd20caa-6f43-4ebe-89eb-757015916060)

*A native automation screen captured from the builder. Automation screens are app screens, but their live state comes from workflow, messaging, approval, and runtime activity rather than ordinary Notion table rows.*

**Data screen types**

Use data screens when the user's main job is to view, create, or update Notion-backed records.

| Screen type             | Use it when                                                      |
| ----------------------- | ---------------------------------------------------------------- |
| List (View Items)       | Users need to browse many records without editing them directly. |
| Details (View One Item) | Users need a focused read-only page for one record.              |
| List (Update Items)     | Users need to review and update multiple records from one list.  |
| Form (Update One Item)  | Users need to edit one existing record through a guided form.    |
| Form (Add Item)         | Users need to create a new record from the app.                  |

**Automation screen types**

Use automation screens when the user's main job is to act on work created by a workflow, understand where work is in a process, respond to a message, recover a failure, launch an operation, or hand work to another app or destination.

| Automation screen    | Use it when                                                                                                               |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Work Queue           | A focused inbox where users claim, complete, or escalate workflow-created work.                                           |
| Decision             | Approval checkpoints where a reviewer chooses Approve, Reject, Request changes, or a similar business decision.           |
| Workflow Status      | Showing where workflow runs are in the process, including waits, retries, completed steps, and outcomes.                  |
| Conversation         | Workflow-aware message threads, comments, replies, and support exchanges tied to a record, route, or conversation.        |
| Exception Resolution | Recovering failed workflow steps, missing data, blocked routes, retries, and manual fixes.                                |
| Notification Center  | Persistent alerts, announcements, reminders, unread notices, and acknowledgements.                                        |
| Automation Launcher  | Controlled manual starts, service requests, operator actions, and launch buttons for workflows.                           |
| Linked App Exchange  | Requests, messages, payloads, acknowledgements, and handoffs exchanged between linked NotionApps applications.            |
| Operator Console     | A high-level dashboard for app owners and operators to monitor runs, queue depth, failures, messages, and audit activity. |

**Everyday chrome screen types**

Use Everyday chrome when users need always-on app shell screens that are not ordinary Notion lists or automation inboxes.

| Everyday chrome screen | Use it when                                                             |
| ---------------------- | ----------------------------------------------------------------------- |
| Home                   | Users need a daily landing surface with next actions and a primary CTA. |
| Search                 | Users need cross-database keyword search from one place.                |
| My Queue               | Users need a personal inbox of work and notifications.                  |
| Activity               | Users need a timeline of submits, decisions, and updates.               |
| Profile                | Users need landing-screen and notification preferences.                 |

Guides for each screen live under [✨ Everyday Chrome Screens](/customize-app/types-of-screens/everyday-chrome-screens.md).

**How to choose the right screen**

Choose the screen by the job the user needs to do:

1. If the user is browsing or editing Notion records, use a data screen.
2. If the user is claiming or completing routed work, use Work Queue.
3. If the user is approving, rejecting, or requesting changes, use Decision.
4. If the user needs to see workflow progress, use Workflow Status.
5. If the user needs to discuss work in context, use Conversation.
6. If the user needs announcements or reminders, use Notification Center.
7. If the user needs to fix blocked automation, use Exception Resolution.
8. If the user needs to manually start an operation, use Automation Launcher.
9. If work moves between apps, use Linked App Exchange.
10. If an owner needs operational health, use Operator Console.
11. If the user needs a Home hub, cross-database Search, personal My Queue, Activity feed, or Profile prefs, use an Everyday chrome screen.

Before publishing, run the workflow or message path that should feed the screen. The screen is ready when a non-technical user can open it, understand what happened, and take the expected next action without support help.

#### When this app needs automation

Use the normal instructions on this page when users only need to view, add, or update data. Use automation when the app needs to do something after that data changes, such as submit for approval, notify a reviewer, route work to a queue, start a conversation, update workflow status, or show a recoverable failure.

Good next steps:

* Automation Overview explains the full maker journey.
* Start From a Wizard is the safest way to create a guided workflow.
* Create your first approval workflow walks through a complete approval setup.
* Native Automation Screens explains Decision, Work Queue, Notification Center, Conversation, Workflow Status, Exception Resolution, Automation Launcher, Linked App Exchange, and Operator Console.
* Everyday Chrome Screens explains Home, Search, My Queue, Activity, and Profile.