Peek/Spy have been designed to have the following features:

   + Peek always warns a user that he is being watched. Peek will also
     periodically remind a user of this while he is being watched.

   + Spy does not warn a user; the user will not know he is being
     watched.

   + Peek users normally must have system privileges (SYSPRV and SECURITY)
     or explicit permission from the user being watched (or from the system
     manager) before they are allowed to watch another user.

   + Spy users normally must have system privileges (SYSPRV and SECURITY);
     users do not grant permission to be watched by Spy.

   + Users who do not have SYSPRV and SECURITY can use Peek/Spy if Peek or
     Spy has been installed with SYSPRV and SECURITY. In this case an
     Access Control List may be used to restrict access.

   + Peek/Spy displays various status information relating to the target
     process and terminal before starting to watch a user.

   + Peek/Spy allows a watcher to browse thru a list of terminals,
     processes, usernames, or everyone on the system. Wildcards may be
     used in these these lists, including wildcards in DECnet nodenames.

   + Keyboard control with Peek/Spy:

         + may be simultaneously shared between both terminals
         + may be passed back and forth between the two terminals
           with only one keyboard active at a time.
         + may be locked so that the watcher may NOT change any
           of the user's data (only with Peek).
         + All keyboard control can optionally be disallowed for
           high security installations (with both Peek and Spy).

   + Peek allows a user being watched to terminate the watching by pressing
     a hot-key. (Only for PEEK, not for SPY.)

   + An output log-file may be created which records all output sent
     to the user's screen.

   + Peek/Spy may be run from a terminal which is connected directly to
     the computer, or thru a terminal server, or from a DECwindows DECterm
     window, or from a DECnet "remote terminal" as created by SET HOST.

     These same types of terminals may also be watched with Peek/Spy.
     (For RTA terminals to be watched, an AXP Peek/Spy $ PEEK/SAVE_SCREEN
     command, or a VAX Peek/Spy $ PEEK/RT_ENABLE command, must first be
     issued from the RTA terminal).

   + A variety of other features allow users and system managers to
     configure PEEK's options to their liking.

   + A journal file keeps track of who's watching who, when the watching
     starts and stops, what terminals are used, etc.

   + Nodenames are supported, including standard VMS wildcards, for
     watching other terminals across a DECnet network, providing the
     target system is also running Peek/Spy.