Administrative Roles

You can configure administrative roles for a chat community on the community's Security tab. This tab allows you to assign the following permissions:

• User..  This is the permission level assigned to all users who want to log on to the chat community as authenticated or anonymous users.
• Sysop..  A chat sysop monitors and controls a chat community's channels from a chat client. To enable a chat sysop, the administrator grants the sysop owner access to a registered, auto-start, or dynamic channel. The sysop can also close a channel by using the IRC Kill command without having owner privileges on that channel. Sysops have no special permissions in a channel unless Chat Sysop joins as owner is selected on the channel's Modes tab.

• Note   To prevent the impersonation of a sysop, only a sysop's nickname can begin with the following strings: "sysop," "orwell," "ChanServ," "CodeServ," "HelpServ," "MemoServ," and "NickServ." For example, any user can use the nickname, "merrysysop," but only a sysop can use the nickname, "sysopmary."

  The terms "system" and "service" cannot begin or be contained in any nickname, including that used by a sysop.

• Administrator..  The Administrator uses administrative commands unavailable to other users. The Administrator becomes the owner of any channel he or she joins, and cannot be denied access to or removed from any channel. The Administrator can also override any action enacted by a sysop, such as a user ban.

• Note   To prevent the impersonation of an administrator, the string "admin" can only be used to begin nicknames used by administrators. For example, any user can use the nickname, "frankadmin," but only an administrator can use the nickname, "adminjoe."

  The terms "system" and "service" cannot begin or be contained in any nickname, including that used by an administrator.