I’m new to bubble and not sure if this topic has already been discussed in another thread but I would really appreciate some input on a database design / choice regarding users and “non-users”.
The app is in it’s essence similar to an internal project management app where there would be users; people that have an account and actively work with the system and non-users; people in the organisation that will be referenced in the app (their names used in tags etc) but the majority will never have the need to log-in.
Both users and non-users are part the the same organisation and I would like to be able to use them in very similar ways e.g. assigning task to them, filtering etc (can’t figure out how to merge lists since they are two different data types.) Additionally I would like to provide the Admin of the app with an easy way to “convert” a non-user to a user when it’s applicable.
Now to my question:
- Should I have two data types? Users and non-users and how should I set-up my workflows to merge these lists? Or should I just keep everything in the user datatype?
- Maybe there is a smarter way of solving this type of problems that I’m not aware of?