✍️ Table

Updated 2026-05-14

Content guidelines

The table component displays structured information in rows and columns. It is the primary way users view, compare, and act on datasets, connections, catalog entries, and other list-based content in the platform.

When to use

To display multiple items with shared attributes that benefit from comparison.
When users need to sort, filter, or act on rows individually or in bulk.
Do not use a table for fewer than three columns or when a simple list or prose suffices.

Column headers

Use short, descriptive noun phrases. Two to three words maximum.
Use sentence case.
Do not use abbreviations unless they are universally understood (for example, “ID,” “URL”).
Do not end column headers with punctuation.
Align header labels with the data they describe — left-align text columns, right-align numeric columns.

Column header examples

✓ Do

Last modified

✗ Don't

Last Modification Date

✓ Do

Owner

✗ Don't

Assigned to / Owned by

✓ Do

Status

✗ Don't

Current status

✓ Do

Row count

✗ Don't

No. of rows

Cell content

Keep cell values concise. Truncate long values with an ellipsis and show the full value on hover via tooltip.
Use consistent formatting within each column — do not mix date formats or number formats across rows.
Dates: use ISO 8601 (YYYY-MM-DD) unless the product context requires a locale-specific format.
Use “None” or ”–” (em dash) for empty values — not blank, “N/A,” or “null.”
Status values use standard vocabulary: Active, Inactive, Draft, Published, Deprecated, Error.

Bulk actions

Label bulk action buttons with a verb that applies to all selected items. For example, Delete selected or Export.
Show the count of selected items near the action. For example, 3 items selected.

Pagination

Label page controls plainly. Use Previous and Next.
Show total result count when relevant. For example, Showing 1–25 of 340 results.