2. Keep Track of Who's Who: Authenticating Users According to Yehuda's report, it's important that a wiki integrate with your existing authentication environment, which could include a single sign-on or LDAP (Lightweight Directory Access Protocol). On an enterprise wiki, there can't be any anonymity when it comes to who edits it. An enterprise wiki should verify the identity of each user so that edits are attributed to the right user. Activity on the wiki needs to be transparent, clear and traceable.

Any enterprise wiki should also have ways in which to set access. Some wikis, for instance, should only be accessed, read and edited by a group of executives, while other more public wikis can be modified by anyone within the company.

3. Give IT What They Want

If you picked an on-premise wiki, you likely did so because it would fill a certain set of IT requirements around data storage and integration with existing enterprise systems. If that's the case, you need to talk to your IT enterprise architects, who can give you the nitty-gritty requirements around what will work (and what won't) for installing an enterprise wiki.

What kinds of things will they consider in finding the right wiki? For one, they might have a certain set of standards and frameworks they prefer for Web applications, and any wiki would have to fall into that category.