Greetings Tracy ~

DNN was built to support multiple logical sites within a single installation (I say logical because the data separation is logical, all in the same DB).  The scenario you describe is a pretty common use case.  There are some basic constraints to understand:

1) A "Host" user (or SuperUser) overseas all sites and is the only kind of user that can add/remove new types of modules.  The intent is to prevent individual site administrators from doing the kinds of things that could disrupt another site.  Similarly, a SuperUser has access to all the higher functions like the Scheduler, default settings, performance settings, etc.

2) An "Admin" user overseas the individual sites and has full access to all the site level administrative functions (including adding/changing pages, site roles, user management, etc).  Now, in version 5, administrative functions can be selectively pulled out... you mentioned isolating User Management specifically.  Although possible in version 4, version 5 will make this much easier by allowing you to create a (non-administrator) role which you can give access to the User Management function.

Cheers

Scott Willhite, Co-Founder DNN

Hello Scott,

Thank you for your reply.

I would like to ask a little more about creating a role to which access to the User Management function can be give.

In our setup, each dealership should have an admin to mange users within that specific dealership only.

To expand on the example above, the admin for the Chevy dealer in Portland, Oregon should be able view and manage users for his dealership only, while the admin for the Chevy dealer in Salem, Oregon can do the same for that dealership – none of the administrators in either dealership can view / manage users outside his/her dealership.

Is there a way accomplish this out of the box in version 5?

Again, thank you for taking the time,

Tracy.