2
0
I have a website which supports multiple organizations having multiple users logging into it. The way the setup currently works is that everyone goes to the same site and provide their organization, user name, and password to log in.
Yesterday, I had the idea that it would be easier if we provided each organization with their own site on the server. So, for example, instead of going to www.example.com and putting in org1, user1, pwd1, they could just go to org1.example.com and put in user1 and pwd1.
This would seem to have the following advantages:
- Easier interface for user. They could bookmark their particular site and only have to enter username and password
- Easier maintenance. Changes to web.config for one org or restarting the site could be done without affecting users from other org's.
- More versatile. Settings can be different for different organizations
However, I'm wondering what, if any, disadvantages there would be?
1You can have a per organization URL while still using one web site if you want. – Brian – 2014-01-10T20:27:12.420