> 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/screens-and-components/types-of-screens/details-view-one-item.md).

# Details (View One Item)

The **Details (View One Item)** screen shows one Notion record at a time. It is the destination users open from a List row when they need the full record, related fields, and optional edit/delete actions.

{% hint style="info" %}
**Who this guide is for**\
Makers wiring browse→details flows. This guide covers every Details builder option on **Content**, **Behaviour**, and **Appearance**, plus how field-level options work in the field inspector.
{% endhint %}

## What the screen is for

### Use Details when

* Users open one record from a List
* You need a read-focused record page with optional Edit / Delete
* Field order and visibility matter more than bulk browsing

### Do not use it when

* Users primarily create records: use **Form (Add Item)**
* Users edit in place across many rows: use **List (Update Items)** or **Form (Update One Item)**
* The page is marketing/help HTML: use **Content**

## What users see in the live app

* Field components in the order you configure under Logic
* Optional Edit control that opens an Update Form
* Optional Delete (when the screen is not primary and Allow Delete is on)
* Maker Filtering only applies when this Details screen is a primary screen

## Add Details in the builder

1. **Screens → + New Screen** → choose the database → **Details (View One Item)**.
2. Add and order fields under **Content → Logic**.
3. On **Behaviour**, enable **Allow Editing** and point to an Update Form if users should edit.
4. From the List screen, set **Open Item On Click → Go to Screen** to this Details screen.
5. Publish and test list→details navigation.

![Builder configuration for this screen](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FgOQxWTKdJGHhUkIJmGZg%2Fdata-1786203142-15-00-builder-hero.jpg?alt=media)

![End-user preview of this screen](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FS3ADCpO7kdB5XJZfvcli%2Fdata-1786203142-16-09-preview-closeup.jpg?alt=media)

## Complete Builder Options Reference

### Content tab

![Annotated builder screenshot: Content](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FMqndrBU3kIzx1p1swmvY%2Fdata-1786203142-17-01-section-content.jpg?alt=media)

#### Logic

![Annotated builder screenshot: Logic](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FHHdZC1bSbHw8w1GIrux4%2Fdata-1786203142-18-02-section-logic.jpg?alt=media)

**Field / component list**

**What it does:**\
Defines which properties appear and in what order (add, reorder, remove comps).

**How to use it:**\
Add only fields users need. Put identity fields first (title, status), then details, then attachments.

**Why / recommended default:**\
A short, ordered Details page beats dumping every Notion property. Empty Logic shows “Add Logic to edit the screen”.

#### Filtering (primary screens only)

![Annotated builder screenshot: Filtering](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FAh1EjWFRjDlpVR1o2o0P%2Fdata-1786203142-19-03-section-filtering.jpg?alt=media)

**Filter rows**

**What it does:**\
Limits which records this primary Details screen can show when opened as a standalone primary route.

**How to use it:**\
Usually leave empty when Details is only opened from a List with its own filters. Use when Details is primary and must be scoped.

**Why / recommended default:**\
Off/empty for typical list→details apps. Prefer list Filtering for browse scope.

### Behaviour tab

![Annotated builder screenshot: Behaviour](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2F9wn1A8lDkY6fTA0zj5XR%2Fdata-1786203142-20-04-section-behaviour.jpg?alt=media)

#### Allow Editing

![Annotated builder screenshot: Allow Editing](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2Ft2buDhZEgcxnmvfVasiY%2Fdata-1786203142-21-05-section-allow-editing.jpg?alt=media)

**Allow Editing / Go to Update Screen**

**What it does:**\
Shows an edit path into a Form (Update One Item) for the same database.

**How to use it:**\
Enable for staff/customer edit flows. Select the Update Form screen.

**Why / recommended default:**\
On when users should change records; off for read-only portals.

#### Allow Delete (non-primary only)

![Annotated builder screenshot: Allow Delete](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2Ft2buDhZEgcxnmvfVasiY%2Fdata-1786203142-21-05-section-allow-editing.jpg?alt=media)

**Allow Delete / Button Text / Ask for confirmation / Delete Confirmation Text**

**What it does:**\
Lets users delete the open record. Available when the Details screen is not the app’s primary screen. Success message is typically hidden for Notion.

**How to use it:**\
Enable only for trusted roles. Keep confirmation on. Use clear button text like “Delete request”.

**Why / recommended default:**\
Off by default. Destructive actions should be rare and confirmed.

#### Screen Visibility Logic (primary)

![Annotated builder screenshot: Screen Visibility Logic](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FcPWWBQa9LhD6RsLwlIqF%2Fdata-1786203142-22-07-section-screen-visibility-logic.jpg?alt=media)

**Visibility status / + Add Logic**

**What it does:**\
Controls who can open this Details screen when it is primary (Users-sheet logic on private apps).

**How to use it:**\
Restrict when Details is a landing surface for a role. Otherwise leave unrestricted and rely on list navigation.

**Why / recommended default:**\
Unrestricted for standard secondary Details screens.

### Appearance tab

![Annotated builder screenshot: Appearance](https://4233028229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FEoxN3Djy7EaNsLpdFDNc%2Fdata-1786203142-23-08-section-appearance.jpg?alt=media)

Details Appearance is intentionally empty: field styles live in the field inspector and app theme lives in Settings.

### Field inspector (not screen tabs)

When you select a field in Logic, makers commonly set:

* Label, Helper Text
* Visibility Logic (when the field shows)
* View/style options for read-only display
* For linked edit forms: required, validation, defaults (on the Update Form fields)

**Why / recommended default:**\
Treat Details as layout + navigation; treat the field inspector as copy and visibility polish.

### Related setup outside the inspector

#### List Open Item On Click

Wire the List Behaviour tab to this Details screen or users cannot open records.

#### Edit Navigation

Details is often hidden from navigation and reached only from lists. Mark primary only if users should land here.

## Recommended default setup

| Setting       | Recommended value                     |
| ------------- | ------------------------------------- |
| Logic fields  | Title, status, key details, files     |
| Allow Editing | On → Update Form (if edits allowed)   |
| Allow Delete  | Off unless trusted role + non-primary |
| Filtering     | Empty for secondary Details           |
| Navigation    | Usually hidden; open from List        |

## Testing checklist

* [ ] List row opens this Details screen with the correct record
* [ ] Field order reads well on mobile
* [ ] Edit opens the Update Form with the same record
* [ ] Delete (if enabled) confirms and removes the Notion page
* [ ] Hidden fields respect visibility logic
* [ ] `View as user` confirms role-appropriate access

## Troubleshooting

| Symptom                    | Likely cause                            | What to check   |
| -------------------------- | --------------------------------------- | --------------- |
| List does not open Details | List Go to Screen wrong / Open Item off | List Behaviour  |
| Blank Details              | No Logic comps or wrong record context  | Content → Logic |
| Edit missing               | Allow Editing off                       | Behaviour       |
| Delete missing             | Screen is primary or Allow Delete off   | Behaviour       |

## Best practices

* Keep Details scannable; push rare fields lower or hide with visibility logic.
* Always pair with List Open Item On Click.
* Prefer Update Form for editing instead of overloading Details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/screens-and-components/types-of-screens/details-view-one-item.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.