> 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/how-to-guides/unique-id-chip.md).

# Unique ID Chip

## Unique ID Chip

### Unique ID Chip

Display Notion **Unique ID** values (for example `RST1`) as a compact monospace **Unique ID Chip** on Details instead of plain body text.

{% hint style="info" %}
**What changed**\
A new view component, **Unique ID Chip**, is preferred for Notion `unique_id` properties. It renders the ID as a clear chip so ticket/restaurant/request identifiers are easy to scan and copy mentally.
{% endhint %}

***

#### What you get

| Capability      | Maker setup                                   | End-user result                       |
| --------------- | --------------------------------------------- | ------------------------------------- |
| Chip display    | Add **Unique ID Chip**, bind unique\_id field | Monospace chip (for example `RST1`)   |
| Prefix + number | Uses Notion’s unique ID format                | Matches what Notion shows on the page |
| Placement       | Details (or view layout)                      | Often near the title / header area    |

![Details with Unique ID Chip (Ticket ID)](https://iili.io/Cwe3bnI.png)

***

#### Before you start

* A Notion database with a **Unique ID** property enabled
* At least one page that already has an ID assigned
* A Details screen and **Reload Data** if the property is new

***

#### Step 1 — Add Unique ID Chip

1. Open the Details screen.
2. **Add component** → **Unique ID Chip**.
3. Bind it to the Unique ID property (for example **Ticket ID**).
4. Set a label if you want “Ticket ID” above the chip.

***

#### Step 2 — Preview and publish

1. Select a record and confirm the chip shows the expected ID (prefix + number).
2. Compare with the same page in Notion.
3. **Publish** and verify on the live app.

***

#### Checklist

* [ ] Unique ID property exists in Notion
* [ ] Unique ID Chip bound correctly
* [ ] Sample IDs match Notion (for example `RST1`)
* [ ] Published Details shows the chip

***

#### Troubleshooting

| Symptom          | Likely cause                              | Fix                                                   |
| ---------------- | ----------------------------------------- | ----------------------------------------------------- |
| Empty chip       | Page created before Unique ID was enabled | Open/edit in Notion so an ID is assigned; Reload Data |
| Wrong format     | Looking at a different property           | Bind the Unique ID field, not a text “code” field     |
| Still plain text | Old Details/Heading mapping               | Replace with Unique ID Chip component                 |

***

#### Related reading

* [Board layouts and Details polish (overview)](https://docs.notionapps.com/guides/board-layouts-and-details-polish)
* [20 Jul 2026 Release](https://docs.notionapps.com/release-notes/20-jul-2026-release)

## Builder options at a glance

This guide teaches a focused maker workflow. For the full screen option inventory (What it does / How to use / Why) and annotated builder screenshots, use the matching **Types of Screens** guide:

* Data screens: [List (View Items)](https://docs.notionapps.com/screens-and-components/types-of-screens/list-view-items), [Details](https://docs.notionapps.com/screens-and-components/types-of-screens/details-view-one-item), [Form (Add Item)](https://docs.notionapps.com/screens-and-components/types-of-screens/add-new-item-form), [Form (Update One Item)](https://docs.notionapps.com/screens-and-components/types-of-screens/form-update-one-item), [List (Update Items)](https://docs.notionapps.com/screens-and-components/types-of-screens/update-items-form), [Content](https://docs.notionapps.com/screens-and-components/types-of-screens/content)
* Everyday chrome / Queue & activity: see the [Types of Screens](https://docs.notionapps.com/screens-and-components/types-of-screens) index
* Automation native screens: [Native Automation Screens](https://docs.notionapps.com/screens-and-components/types-of-screens/native-automation-and-operational-screen-guides)

### Recommended defaults

* Change one option family at a time, then publish and test on phone and desktop.
* Prefer screen-level settings in Content / Behaviour / Appearance before custom CSS/JS.
* Keep public access and navigation visibility intentional on every screen you link from this guide.