Ok, not sure what is the right/best way to go about designing this. I need a database that allow a User (admin) to own many Company and a Company can have many Property. A User can also create multiple users (non admin) to help manage certain Company and/or Property. For example, "Company A" have "Property A", "Property B", and "Property C". The admin assigned the new user to manage "Company A", along with "Property A" and "Property B", but not "Property C". Another example might be, a new user can only manage Property A, B, or C, but not "Company A". I hope all you guru understand what I am trying to say. Thanks in advance.
I'd create a total of six tables. Three tables for objects, one table for each of the kinds of objects you're tracking (users, companies, and properties). Three tables for relationships, one for company-owns-property, one for user-manages-property, and one for user-manages-company. I would probably want to include attributes in the relationship tables to show when each relationship starts and ends, since there are often problems when
I don't keep track of that!