It seems you would create multiple portals, one for each company. Each portal and its users are independent of the other. So, lets say you had 2 companies: Company A, Company B. You would have User 1 and User 2 in Company A, Users 3,4 in Company B. While all the data is stored in the same database, each portal really knows nothing of the other (meaning User 3,4 cannot sign into Company A site and content is not shared between sites). Is this not what you are trying to achieve (you could use subdomains for naming, like companya.domain.com and companyb.domain.com)?

---

Chris Paterra

Get direct answers to your questions in the Community Exchange.

Hi Sebastian

Thanks for the response...

Our objective is to create an ERP-kind of package able to handle multiple companies and the basis for this should be a solid framework like DNN. I want to concentrate writing on core business logic and let the underlying framework handle the other work for me.

Our package should be able to support the multi-company feature. Let me explain you with the help of an example.

For instance, a system admin. should be able to create a high-level entity: Company-X and below it User1 (belonging to Dept 1) and User2 (belonging to Dept 2) should be there. Another high-level entity: Company-Y and below it User1 and User2 should be there.

Also, the underlying framework should be able to distinguish between the respective data they create. For instance, we should be able to identify that the PO order # 100 has been created by User 1 belonging to Company-X and PO order # 101 has been created by User 1 belonging to Company-Y.

If I am correct, the departments will boil down to groups and the DNN has this functionality to offer.

But I am afraid that the multi-company feature is not implemented in the DNN. If it is, pl. elaborate. If not, pl. tell me if there is a solid workaround or how easy/difficult will it be to customize such a thing.

Looking forward to hear from you.

Thank you once again
Raman D.