Since a Tenant User can only be created via additional values when creating a user via PUT api/users, or created from an existing user via PUT api/tenant/{tenantId}/users which has to include the UserId, why do we also need to have “email” in the tenantUser model ?
It seems that email is a property that in all respects only exists as an attribute of a User - it can’t for example be updated via api/tenant/{tenantId}/users.
I understand that in the UI it’s nice to work with users by their e-mail attribute, but it seems strange that this leaks into tah API model. Not a big issue, just a bit confusing when working against the API