1. Modify the unit's security rules to be more restrictive (under the access control... > rules... menu). Security rules determine what the unit can and cannot do, as well as who can make the unit perform various tasks. For example, setting the unit privileges "run away" and "safeword" to 6 (the default) enables these actions, but 0 disables them. For most other rules you will want to set them to 5 (owner only) for a private unit, or 1 (no consent required) for a public-use unit.
2. Add a self-ban (under the access control... > bans... menu) to stop the unit from using itself. This prevents execution of all commands and access to all menus. However, it also interferes with some administrative actions like updating the operating system to a new version.
3. Make sure the user has an ARemote console. This allows easy menu and command access from anywhere in the region. ARemote consoles can be purchased from this location in the Nanite Systems main store in Eisa for L$200 and may be transferred to other SL accounts after purchase.
4. Use triggers. These are verbal commands. For example, an authorized user might say something like, "doll, go home", in local chat to make the unit teleport to a prearranged location. The ARES command reference explains how to set up triggers in detail.
5. Enable policies. These are various behavioral restrictions not covered by the standard power subsystems, such as preventing the unit from changing its outfit or forcing it to wear a certain group tag. Policy control can be found in the settings... > policies... menu.
   As of ARES 0.5.4, not all policies are implemented yet.
6. If you own a lot of ARES units, consider creating an XNMS domain. XNMS allows for an administrator to configure and manage multiple units using a single server. After each configuration change on the server, affected units are marked as "out of date" and will automatically be reconfigured the next time they enter the home region. XNMS is similar to provisioning systems for conventional computers such as LDAP, Active Directory, NetInfo, and NixOS.
   Although domain support existed in Companion, it is only scheduled for implementation after ARES 0.5.7 ships. (See roadmap)
7. Track your unit using myNanite UPLINK. This is a subscription-based web service that allows the user to run commands, use menus, and interact with local chat from any modern browser, including mobile. Designed for 24/7 total power exchange enthusiasts, UPLINK's flexible licensing model includes options for couples, promiscuous units with many users, and playboy/playgirl users who interact with many units.
   myNanite UPLINK is scheduled for release during the ARES 0.7.0 update cycle. (See roadmap)
8. Feeling brave? Try looking at the power settings. Unlike most robot systems, the RLV restrictions used by ARES to implement different power states are 100% customizable, and may be rewritten, removed, or supplemented as appropriate to the unit's duties. Even the source code to the power management system is available as part of the ARES software development kit if you would like to alter, for example, the overlays displayed on screen while the unit is powered down.

Previous Tutorial: Configuring ARES for a sex robot

Next Tutorial: Dealing with bugs and unexpected behavior