Export (0) Print
Expand All

Group Chat Server Best Practices

 

Topic Last Modified: 2011-01-23

As you create your categories and chat rooms and assign scope and membership, the following tips might help your planning:

  • If you want all categories and chat rooms to follow a global behavior, make that setting at the root category before you create any subcategories, and have all subcategories and chat rooms inherit it.
  • Avoid placing chat rooms in the root category, unless they are public announcement channels.
  • In most cases, you should allow users to create new chat rooms so that discussions about new topics can be started any time.
  • If your company does not require an ethical wall and you are not granting federated users access, do not narrow the scope in your category tree. Put all your users in the scope of the root category, and let that scope be inherited all the way down the tree. Then, use only membership lists to grant or restrict access to each chat room.
  • Give each chat room a complete name and topic summary that describes where it fits in to your organization. Because users cannot see the category name when they use the chat room, you cannot rely on the category name to help users determine the intended discussion forum for the chat room.
  • You might want to include “Public” or a similar word in the name of every chat room that is open to federated users, to remind your organization’s users that these chat rooms include members from outside the organization.
 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft