Hi,
We are in the phase of designing an application based on aspnetzero and this question here is related to the application Business Logic design based on the aspnetzero schema. Though, most of the Business Logic is already converted to the aspnetzero schema, however there are a couple of things that I'm not sure of and that's why I'm asking you if you have any suggestions in this regard.
The application involves a Vendor entity, the application will hold the products and staff users for those vendors. The application will also hold the customers user data and our staff users. The design decision we took for users is to store all different users in the default Abpusers table. The application is going to be a single tenant application holding all the different kind of users, vendors and products.
Now the design decision to make is how the vendors should be managed inside this application. The critical business rules for vendor entity is that the vendor staff can only see/manage the products and users related to that vendor, nothing else. The customers can be linked to any vendor by our staff users. In essence, what we want is that when a vendor user logs in to the application, he can manage everything related to that vendor, when our staff member logs in into the app, they can manage everything. So the question finally is that can we use organization units, permissions or anything else to implement this kind of logic, or do we have to implement custom logic for this? It'd be great if we can use the pre-built administration pages for our staff members and vendor staff members based on the business logic I've shared above.
Thanks,