>A user might be member of multiple portals (with individual user profiles), but you need to provide him with a company switcher etc.
A use will be a member of one and only company (portal in terms of DNN). Yes, the system should have the ability to send his data to a user of another company. This can be implemented using the workflow feature. Right? In other words, the users of other companies should be able to view his data. Is it possible, if we adopt the sub-domain option.

>Custom modules may easily be build to support multiple portals as individual companies.
By multiple portals, do you mean the sub-domains like companyA.website.com?

By custom modules, do you mean to say the modules comprising our core business logic? Or, do we need to customize the DNN itslef in order to assign one sub-domain (portal) to one company?

>This approach will allow you to create individual web sites per company
The company A will access with this URL: companyA.website.com

With Regards

Robert

Thanks. This is some info. that will help me get on the track. But I am still halfway through being new to DNN.

>We actually modified the core user object to include a company ID. At this point I would recommend against that, because of the upgrade hassles. (the changes were not that great but it was enough to cause some headache)

I did the same mistake in the PHP-based huge code base and completely closed myself to upgrades. I made the changes in about 2K places but it was done using a script.

However, at how many places did you make the changes. If in one single class, then I believe it won't be difficult to keep it in sync with the upgrades.

>I would suggest you just create database tables for companies then a table that relates users to the company (or companies) and a module to handle those mappings. Then you can use that info in any modules you create.

The backend part I got it. Pl. elaborate what kind of info. would need to be there in the module that handle those mappings. Pl. give an example. In other words, what will be the functions/methods like of that module.

>The out of the box DNN modules will be unaware of your mappings though. (along with any other 3rd party modules)
Yes. Or, can't use inheritance to extend them, if required.

>I would not create separate websites or subdomains for each company. That is a maintenance nightmare.
I am of the same viewpoint.

I am really looking forward to hear from you.

Thanks
Raman