Port currently supports JSON-based filters at the widget and page level, but not at the dashboard level.

This limits important personalization use cases. For example, we wanted a dashboard table to default to showing entities from a blueprint that are related to the logged-in user, while still allowing the user to clear the filter and see all entities. A dashboard is the right UX for this, but since dashboard filters don't support JSON, it isn't possible today.

Adding JSON support for dashboard-level filters would:

Enable personalized dashboards

Make filtering behavior consistent across widgets, pages, and dashboards

Allow teams to define smart defaults without removing user flexibility

If dashboard JSON filters aren't possible, a strong alternative would be a built-in "Me" user entity representing the current logged-in user, so dashboard filters can support user-specific default views.