Creating fields definition with filled out choices for any target (account, user, application) and than creating corresponding instance trough api endpoints with filled out field that is not defined in choices, will be accepted and shown in the view.

When using "Signup" endpoint with having "Account" as well as "User" fields definition having the same name, it updates both of them. There is no distinction between which definition is for the Account and which for Admin user when sending "Signup" request. Making potential problems when having different choices.