Pin the Pagination Bar or Enable Infinite Scroll for Grid Reports

1. The problem
Grid-style reports on HubSpot dashboards force users to page through data because:

The pagination bar disappears behind an inner scrollbar whenever the table is taller than the tile.

There is no option to load all rows in a single, continuously scrollable list.

Both issues slow down analysis and create friction for teams that review long tables daily.

2. Requested enhancement (either/or)
Option What it does Ideal settings
A. Pin the pagination bar
Keeps page controls fixed at the top or bottom of the grid so they’re always visible, even when the table scrolls. - Toggle “Pin pagination bar”
- Choose Top or Bottom placement
B. Enable infinite (full) scroll Loads all rows in the DOM and lets users scroll through the entire dataset without paging. - Toggle “Show all rows (infinite scroll)”
- Soft cap or warning if the row count could hurt performance
Either solution eliminates the extra click-scroll-click cycle. HubSpot could ship both and let report creators pick the behaviour that best fits each dataset.

3. Expected benefits
Faster navigation – one smooth motion to view more data.

Cleaner dashboards – removes confusing nested scrollbars.

Accessibility – screen-reader and keyboard users find controls immediately.

User choice – admins tailor each grid for performance or convenience.

4. Who needs this
RevOps and Sales leaders scanning long opportunity or activity tables.

Marketing teams reviewing asset performance across many campaigns.

Support managers auditing ticket queues during stand-ups.

5. Success metrics
↓ Time-to-first-click on navigation controls.

↓ Internal “can’t find page numbers” support tickets.

↑ Adoption of dashboard grids versus exported spreadsheets.

6. Suggested implementation notes
Pinned bar: place pagination inside a position: sticky container within the iframe; maintain current styling.

Infinite scroll: virtualise rows to minimise DOM load; warn users if a report exceeds a safe threshold.

Preserve existing behaviour as the default so current dashboards stay unaffected.

Thank you for considering these two complementary paths to smoother, more user-friendly dashboards!

Wish I could upvote this more than once.