Port recently introduced the ability to lock catalog pages so that member role users cannot edit columns, filters, etc. We'd like to extend this functionality to entity pages as well, preventing users from modifying which properties they can view.

Currently, users can access the "Manage Properties" button on entity pages to display any property from a blueprint, even those intentionally hidden by administrators. This is problematic when blueprints contain properties used for backend calculations or integrations that shouldn't be visible to end users.

Adding page locking to entity pages would provide consistent administrative control over data visibility