Design For Profiles

0
Hello,  I am wondering what is the best practices for designing user profiles, so that everyone can have an organized view. In our case the users will be companies signing up for the solution and other individual users underneath it. I know that you can use XPath constraints to limit visibility to things only they are related to, but I want them to be able to interact with other companies within the application and selectively share data with one another. Do these XPath constraints cause any performance issues, and should I just be making a reflection of the "account" entity so that I can add other specific details per user or simply relate back to it?    Any recommendations are greatly appreciated.    Thank you, Alex 
asked
1 answers
0

Hey Alex,

Great Question !! So, The cleanest approach is to keep the built-in Account just for login, and then link it to custom entities like UserProfile and CompanyProfile where you store all the business details.

db model.png

Think of it like this:

  • Company = organization

  • UserProfile = people in it

  • Account = how they log in

  • Project = work they do or share with others

For cross-company sharing, use associations (or a “sharing” entity), And don’t worry too much about XPath — it’s the standard way to filter data in Mendix and only becomes heavy if you’re working with really large or complex datasets.This way, login stays simple, data stays organized.

 

Regards 

Reemali

 

answered