Beyond browsing, searching, and editing one row at a time, a Data Table block can turn on several optional, end user facing features from its own block settings. Every toggle below is off by default, turn on whichever ones fit your app, each is independent of the others except where noted.
Bulk actions
Turning on "Let visitors select multiple rows for bulk delete/update" adds a checkbox per row and a header checkbox that selects every row on the current page. Once one or more rows are selected, a bulk action bar appears above the table, a bulk delete (which asks for confirmation first) if the block's own "Let visitors delete their own records" setting is also on, and a bulk "set one field to one value across every selected row" update if "Let visitors edit their own records" is on. A visitor can only ever select and act on their own records, even on a table showing everyone's or an organization's records, the same ownership rule that already applies to the single row Edit/Delete buttons.
Saved views
Turning on "Let visitors save/reselect a named search+sort+column view" adds a "Views" dropdown and a "Save view as..." button above the table. A saved view remembers the current search text, sort column and direction, and which columns are shown and in what order, giving it a name saves all of that together, reselecting it later reapplies the whole set in one click. A view can optionally be shared, visible and reselectable by anyone else who can see this table (never a way to see records a visitor couldn't already see, only to reuse a search/sort preset), private views only ever show up for the person who saved them.
Columns
The same toggle as saved views above also adds a "Columns" menu letting a visitor show or hide, and reorder, whichever columns you've configured on the block. This is a personal preference remembered on that visitor's own device between visits, separate from a saved view unless it's actually included when saving one.
CSV import
Turning on "Let visitors bulk create records from a CSV file" (this also needs "Let visitors edit their own records" on, the same write gate every other way of adding a record already uses) adds an "Import CSV" button. Picking a file shows a mapping step, each column from the file next to a dropdown of your collection's configured fields, so a visitor (or you, testing your own app) can line up mismatched headers before confirming. After confirming, a result summary shows how many records were created and how many rows were skipped and why (for example, an empty row). An import is capped at 2,000 rows per file, split a larger export before importing it. Excel (.xlsx) files aren't supported yet, only CSV, export a spreadsheet to CSV first.
Tip: Bulk actions and CSV import only ever touch records the signed in visitor actually owns, never someone else's, no matter what the table's own scope setting shows them.