Current Behavior: When adding a property of type "User" via the UI blueprint editor form, Port automatically converts it into a relation to the _user blueprint instead of saving it as a property. This happens regardless of the blueprint or property name chosen.

Desired Behavior: Users should be able to create a User-type property (not a relation) directly from the UI blueprint editor form, with the same result as defining it in JSON mode.

Impact:

The inconsistency between the UI and JSON/API/IaC methods is confusing and undiscoverable — users are not warned that the UI will silently convert their property into a relation.

User-type properties created as relations cannot be mirrored to child blueprints, limiting their use in reports and widgets (e.g. Pie Chart breakdowns).