> For the complete documentation index, see [llms.txt](https://docs.scaleflex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleflex.com/portals/portal-settings/datasets/dataset-pages.md).

# Dataset pages

Give every row of a dataset a page and a URL of its own.

A list shows many rows at once. A **dataset page** shows **one** — the row named in the URL — so a press release, a job opening or a product gets a page a visitor can link to, share and find.

You build it once. Every row then renders through it at `/{page}/{row-slug}`.

## When to use one

When a row has enough to say to deserve its own page: a full article, a job description, a product with specifications. If a row is a line in a list — a changelog entry, a contact — a connected list is enough, and the row's anchor already gives it a link.

## Create one

1. Open the page selector and select **Add new page…**
2. Choose **Dataset page** as the **Type**.
3. Pick the **Dataset** the page reads from.
4. Fill in the name, slug and title, then **Add**.

{% hint style="info" %}
**Dataset page** only appears as a type once the Portal has at least one dataset — there would be nothing for the page to read. If you can't see the option, make the dataset first.
{% endhint %}

An existing page can be converted: **Edit** on the page's menu switches it between a web page and a dataset page.

## Putting the row on the page

Build the page out of sections as usual, then bind the parts that should change per row.

1. Select the text you want to come from the row.
2. Choose **Connect** in the text toolbar.
3. Pick the field.

Bound text shows the field picker with that value; unbound text offers the connect button again. Everything you don't bind stays as you wrote it, identical on every row — which is how a shared heading, a standing disclaimer or a contact block works.

The binding is resolved on the server, so the row's words are in the page's HTML rather than filled in afterwards. That is what makes them indexable.

## Beyond text

Two more kinds of section can follow the row:

* **A gallery** in Flat mode can show only the entry's own assets: pick the row's **DAM assets** field under **Assets of this entry** in the gallery's [Source](https://docs.scaleflex.com/portals/building-a-portal/sections/gallery/gallery-settings/source.md) settings.
* **A list** connected to the same dataset can leave out the entry being shown, or list only the rows that share one of its values — *more from this collection*. See [Criteria](https://docs.scaleflex.com/portals/portal-settings/datasets/connect-to-dataset/criteria.md).

## What the canvas shows

A dataset page previews the **first published row**, with a banner naming the dataset and the row being shown, and a **Change** control to preview a different one. A visitor who opens the bare page without a row in the URL sees that same first row.

## Links from a list

When a list is [connected to the same dataset](https://docs.scaleflex.com/portals/portal-settings/datasets/connect-to-dataset.md), a link on one of its rows goes straight to that row's page — you link to the page, and the row's slug is appended for you. A list connected to a *different* dataset links to the bare page instead.

## Good to know

* The page's title comes from the dataset's **title** field, or its first text field if there isn't one.
* Which row a URL resolves to is matched on the row's slug — see **Row anchor** in [Context](https://docs.scaleflex.com/portals/portal-settings/datasets/connect-to-dataset/context.md).
* Drafts are visible to you in the builder but never to visitors, exactly as in [Items](https://docs.scaleflex.com/portals/portal-settings/datasets/items.md).
* A bound text's [**Format**](https://docs.scaleflex.com/portals/portal-settings/datasets/connect-to-dataset.md) applies here as it does in a list — an option's label, a date's style — except **Relative**, which shows the plain date: the page is rendered once and cached, so *2 days ago* would go stale.
* The global header, footer and sidebar banner render on every page, so they are never bound to a row.

{% hint style="warning" %}
Not everything is bindable yet: button labels and their links are not, and Spotlight experiences are not. Media bound outside a list shows its stored image in the builder while rendering the row's own media on the live Portal.
{% endhint %}
