The server can either alert the entire network when the clone limits are triggered or it can just alert the operators on itself. The default is to only send alerts locally.
/as security clone alert network
If your server is part of a network where you trust any of the operators to deal with your clones, then it may be better if all servers report globally. However, it would depend on how many clone alerts the network tends to get and how much you want other operators doing with your clients.
The server can search for clones either only among its own users or on the entire network. The default is to only search locally.
/as security clone detect network
You will probably want to leave detection local. But, in theory, you could set detection to network and alerts to local and only authorize operators on that one server to deal with clone alerts. The advantage of this would be that other operators would not have to deal with the extra scroll and you could have people specialize. The disadvantage is that if a server were to split off, nobody would be dealing with its clones.
This command sets the default level for searching for clones. Triggers will still take precedence for specific hosts. The default is 10.
/as security clone level 12
Clone level is always a compromise. If you set the value too high, you will miss too many clones. If you set the value too low, you will be investigating too many innocent users. Ten tends to be a decent amount, but you can experiment and see what works best for your server.
This command will turn off clone detection for the server.
/as security clone off
You would probably only want to turn off clone detection if you are part of a network where another server is watching for clones over the entire network. While clones won't be a major problem for most networks, if ignored they may become so.
This command will turn clone detection back on.
/as security clone on
This is useful if you temporarily turned off clone detection for some reason.