I am trying to help out our web team after the person previously running it left the company.   I don't know all that much about DNN but our implementation looks like a big heap of confusion to me.  For whatever reason, he created everything as new sites under the root.  Say our website is www.blah.com.  The HR department has a website www.blah.com/hr. The operations department has www.blah.com/operations.  User Bob has www.blah.com/bob.  User Jack has www.blah.com/jack.  Multiply all those by 200. And each one of these is a new site.  BTW-is a site the same as a portal?

 My thinking is that, for the above scenario, we might have 2 sites:  departments and users.  The end result would be www.blah.com/departments/hr and www.blah.com/users/bob.  I prefer this way of doing things because it's more organized (in my mind).

And yes I will RTFM but this a live website and we need to get it squared away asap.  Currently, this multitude of sites is causing problems with our AD Authentication Pro module.

I appreciate any guidance.

 -Roger

As far as I can tell, we aren't using any profile modules. I see the ViewProfile module but it's not used anywhere.  I do agree that profiles seems like the logical place for this--if we had them set up.   I'm assuming that, when new users log in, their profile page is created automatically. That would eliminate the need to have to create them manually and assign permission accordingly.  I will have to bring this up to the team and see why we aren't doing that.

 I'm not sure if your suggestion for departments would work for us.  You aren't talking about using sites or sub-sites, right?   If I created a department named IT, I know I can assign permissions to that page, but would I be able to assign permissions to the IT web developer to create sub pages as you said? 

Thank you for your responses!