Thread:Project:Support desk/Best approach for wiki supporting multiple discrete projects/users?

I am in the process of deploying a wiki containing help and training pages for multiple software applications. At this point we have one wiki installed and have created all of the content for one piece of software, and are just beginning to create the content for a second piece of software. Ultimately I expect to host content for possibly up to 50 different applications. Each application has its own user base, but virtually all users will need access to the content for a second program, and in rare cases a third. Also, we have internal users who will need access to all of the content so I believe it imperative to have a single sign-on. However, it is strongly preferred by management that we be able to limit what content our wiki users have access to. The site will be password protected and anonymous access is blocked, so users are required to login. What I'd really appreciate are suggestions on the best approach to structuring the wiki(s) and controlling access. I have near complete flexibility about what gets implemented (although I will have to have solid justification for all changes), and we have not given access to any external users at this time. So, any suggestions about either structuring the content within a single wiki, or deploying/managing multiple wikis would be appreciated.

Thanks