PRIVILEGE

Usage: PRIVILEGE <command> [<level>]

ADMIN - Server Administrator (flag a)

COST - Flood Cost of Specific Commands

HELPER - Helper (flag h)

IRCOP - Operator (flag g)

NONE - Disable command

OPEN - Set command back to default.

SA - Services Administrator (flag s)

This command allows you to customize the access level for server commands. If you set the access level to NONE then the command is no longer allowed on your server. OPEN allows anyone to use the command. 
This way you can customize the responsibilities and privileges that go with different levels of access as you see fit. You can restrict a command more than its default but opening a command may not always allow users to execute the command.

Examples:

/as help privilege <topic>

A few commands are locked because altering them is a very bad idea. For example, if you could set the privilege for oper to anything other than open then no one would be able to oper to get his or her privileges. The default privileges for each command are designed to be generally practical, but since different networks will work in different ways you may well prefer to limit some commands. 
Be very cautious when making a command more open though. Most commands currently restricted to operators are restricted because they can be abused if they are open.

Usage: PRIVILEGE <command> ADMIN

This command will set the specified command to only allow admins (+A users) to access it.

Examples:

/as privilege nflash admin

One of the many access levels that you can set commands to when customizing your server. This allows you to have many levels of trained staff on your server without fear that they can access commands that should not be used.

Usage: PRIVILEGE <command> COST <low|medium|high>

Sets the flood cost of each command specified.

Examples:

/as privilege info cost high

There are some commands that you really don't want used very often, and some commands which don't need to be used often. The LIST command on a large network can be quite expensive to use for both the CPU and your servers bandwidth, and so you'd want to set that command with a high flood limit.

The INFO command is one that has only infomrational use and once issued really doesn't need to be issued again. Where the INFO command is not expensive to the server it is a command that doesn't 'need' to be used and so you could make a case that it should also have a high flood penalty.

In the end you will need to decide what is the right balance for your server and environment.

Usage: PRIVILEGE <command> HELPER

This command will set the specified command to only allow helpers (+h users) to access it.

Examples:

/as privilege whois helper

One of the many access levels that you can set commands to when customizing your server. This allows you to have many levels of trained staff on your server without fear that they can access commands that should not be used.

Usage: PRIVILEGE <command> IRCOP

This command will set the specified command to only allow operators (+o users) to access it.

Examples:

/as privilege list ircop

One of the many access levels that you can set commands to when customizing your server. This allows you to have many levels of trained staff on your server without fear that they can access commands that should not be used.

Usage: PRIVILEGE <command> NONE

Removes the command from the server.

Examples:

/as privilege lflash none

Usage: PRIVILEGE <command> OPEN

This will allow all users on the server to access the specified command.

Examples:

/as privilege who open

Use this when you want any user to be able to access the specified command.

Usage: PRIVILEGE <command> SA

This command will set the specified command to only allow services admins (+a users) to access it.

Examples:

/as privilege info sa

One of the many access levels that you can set commands to when customizing your server. This allows you to have many levels of trained staff on your server without fear that they can access commands that should not be used.