Problem Statement

When using create_catalog_page: true to automatically generate catalog pages for blueprints, these pages display all entities to all users by default, regardless of team membership. Currently, there is no automated way to apply the dynamic "My Teams" filter at page creation time via Terraform or API.

Current Limitations

Manual Overhead: Customers must manually apply and save the "My Teams" filter in the UI for each auto-generated catalog page, which is not scalable when managing multiple blueprints.

No Terraform/API Support: While the dynamic "My Teams" filter exists in the UI and initial filters can be configured for pages, there's no way to set this as a default behavior for auto-generated pages programmatically.

Inconsistent Experience: Without automation, ensuring all users see only their team's entities requires ongoing manual configuration, creating operational overhead and potential security gaps.

Requested Feature

Add support for automatically applying the "My Teams" dynamic filter to catalog pages created via create_catalog_page: true, either through:

A configuration option in the blueprint definition (e.g., default_team_filter: true)

A global setting that applies to all auto-generated catalog pages

Enhanced Terraform provider support for setting initial filters with dynamic team context on page creation

Expected Outcome

When a catalog page is auto-generated for a blueprint, it should automatically filter entities to show only those belonging to the logged-in user's teams, without requiring manual UI configuration for each page.

This feature request addresses the automation gap for team-based filtering at scale and aligns with Port's existing RBAC and ownership capabilities.