The “Future Arrivals Only” filter on the Invitations table is component-local state and resets on every page load. In peak season this customer has hundreds of future arrivals and re-applies the filter on every visit. She had resorted to deleting past invitations to keep the view clean, which destroys the guests’ guidebook links and view counts.
Requested: persist the filter selection as a user preference or saved view (or a default-view setting). Same behaviour applies to legacy and new Hub, since both routes render the shared Invitations component.