---
title: Data
customers-call-it: feature
url: /docs/features/sites/site-features/data
---

# Data

Show rows from your tables on your website, using only the columns and rows you choose.

## Use it when

Use it for dated listings, calendars, people, supporters, job openings, questions and answers, captioned photos, services, projects or other content maintained as rows. A table is one CMS item; its different website placements and conditions sit inside that item's website settings. Site content does not get a separate business sidebar feature.

## How to add a section

1. Open your site in **My Sites**.
2. Under its sidebar, press **Add item**.
3. Press **Add to site**.
4. Choose the thing you need: **Dated rows**, **Calendar**, **People**, **Supporters**, **Job openings**, **FAQ** or **Photos**, or another available section.
5. Choose **New table** and its type/name, or **Use existing table** to keep using your authoritative records. Check the columns visitors may see and any row condition.
6. Press **Review changes**, then check what it will make or reuse.
7. Press **Apply**. The table appears in the site's sidebar. Nothing is published.

See [Dated rows](/docs/features/sites/presets/dated-rows-section), [Calendar](/docs/features/sites/presets/calendar-section), [People](/docs/features/sites/presets/people-section), [Supporters](/docs/features/sites/presets/supporters-section), [Job openings](/docs/features/sites/presets/job-openings-section), [FAQ](/docs/features/sites/presets/faq-section) and [Photos](/docs/features/sites/presets/photos-section) for each shape's defaults. Event calendar and Wedding calendar remain named table types with their fitted record windows; they use the same section mechanism.

## How to change which rows and columns show

1. Open the table in the site's sidebar, then its placement under **On the website**.
2. Under **Shows only**, choose a **Column to filter**, its **Condition** and a value, then press **Add condition**. **Is any of** takes values separated by commas; a date column also offers **Upcoming** and **Past**, which sets the corresponding date order. Every saved condition must match a row for it to show. **Remove** widens the rows shown: keep publication and privacy conditions unless you intend to change them.
3. Change **Order** and **How many**. Under **Public columns**, map only the content visitors may see; optional parts can be **Not shown**. Keep the website label rather than a private name for private-event calendars.
4. Press **Save**, then preview the draft. Existing authored markup keeps its appearance. After adding or removing a displayed part, explicitly put the section on a page again to update its markup.

After placement, **Fields** also lets you change which column supplies an existing placeholder without rebuilding that page. Fields are text or permitted assets, never executable page code. Team notes and record bodies are not automatically made public.

## How to put it on a page

1. Open the table and its placement under **On the website**.
2. Choose the **Layout** and any explicit search, filter chips or booking links under **On the page**. A calendar's minimal default shows only the selected date and words; booking links start off.
3. Press **Put on a page**, choose the page, then press **Put it here**. It adds the section at the end of the page's main content or replaces that same use's section already there. Review a replacement when you have custom markup.
4. Preview, then press **Publish** when ready for visitors to see the draft.

## How to give each row its own page

Open the placement and press **Give each its own page**, then preview the generated addresses before publishing. A title/slug column supplies the address. **Stop making pages** stops that use's page family without deleting the records. **Remove from site** removes the placement and its sections, not its source table.

## Example

A community centre uses one Dates table for public workshops and closed days. Its Calendar placement shows only the website label and date; a Dated rows placement also shows approved descriptions and booking links. Its FAQ and captioned Photos tables live in the same site's sidebar, not as extra business-level features.

## If something isn't working

- **A column or table is refused.** Pick a readable table in this business and map its actual column IDs. The checked owner does not copy another business's data or silently add missing columns.
- **Nothing is listed.** Check every condition, date, count and row value, then prepare/preview again. Empty lists show the section's no-content wording.
- **A dated section asks for a time zone.** Set the business's time zone in Business profile. A date-only column uses that local day; a timestamp uses the current instant.
- **A photo has no description.** Add an image description to its row and choose the description column under Public columns. Captions and credits are separate; none is invented.
- **Choosing between an older and a general section.** Existing Upcoming/Past shows, Team/Board/Staff profiles and Grants remain available and keep working. Prefer Dated rows, People or Supporters with matching settings for a new placement. Adopting a new type for an existing placement is a separately reviewed draft change, never another new table.
- **The draft changed while saving.** Reload and review the latest draft before saving again; publishing is separate.

## Limits

- At most 16 uses per draft, 1–200 rows per section and the existing 200-row-page bound. Section defaults are 50 dated rows, 200 calendar days, 48 people/supporters, 24 jobs, 50 FAQ answers and 60 photos.
- Date conditions and source rows are resolved when Sites prepares the page, not by the visitor's browser clock. Source changes use the platform's existing refresh path; a Drive-folder Gallery remains an explicit frozen snapshot, not a live row list.
- Removing a placement does not delete its table or rows. Changing the catalogue does not rewrite saved Versions or existing custom markup.
- Nothing sends, spends or publishes automatically. A listing is not a booking service, application inbox or payment checkout.
