1

Hello,

I am trying to make an marketplace app that sells a digital product that should be editable by the purchaser, but am struggling to design the database efficiently.

I currently have the type of user set up as a field on the default user data type that is populated through the signup workflow. This field determines what type of dashboard the user sees when they pull up the page.

I am struggling to understand how to offer the ability to change a field of a data type relative to the specific user and user type. I could create two different fields for each piece of information, but that seems very clunky.

For example, I would like a date range to be able to be set for the product. The store owner should be able to set their date range, but the user should be able to modify it for their own purposes.
My current idea would be to have two fields: 1. Date_Range_Customer, 2. Date_Range_Purchaser. Then, I would populate Date_Range_Purchaser with the data set in Date_Range_Customer (the master list) and all changes to the Date_Range_Purchaser would be specific to that user.
Edit: the more I think about this the less I think it would work how I am planning

Similarly, the store owner will specify a list. I would like the user to be able to change/edit the list without changing the store owners list.

How is the best way to do this?