During initial setup (such as when you first download PAM) various parameters need to be configured for the executive to function properly. These are best set using a text editor to edit the startup file for PAM. The startup file is in the same format as the checkpoint file that PAM creates. As of PAM Build 37 it is create manually using a text editor. Future versions of PAM may include a startup "wizard" to simplify this initial setup.

PAM updates the file when it checkpoints. Checkpoints can be created manually from the local administrator's interface. Checkpoints can also be created automatically and periodically via a checkpoint daemon. PAM will make an extra copy of the first checkpoint created every day to help recovery in case of catastrophic failure. A "history" of checkpoint files that is up to one month old is automatically maintained by PAM, provided that the checkpoint daemon has been created and is enabled.

Channel building is performed using Bert. Bert cannot edit daemons, only Sources, Handlers, and Outputs (also knows as PIMs, Jugglers, and DIMs).

Administration is performed using the local GUI that is built into the PAM image. The local gui allows the administrator to see lists of active and inactive sources, handlers, and outputs. The administrator can examine all attributes and configurations. The administrator can quickly identify the state of execution and the time at which various agents are scheduled to run. The administrator can change any setting on any agent. As of PAM build 37 the administrator has access to all passwords.

Browsing is performed using commercial browsers and client tools such as with an email client, a BackWeb client, or a Castanet client. The administrator must configure PAM channels to use the appropriate output modules to move information to the appropriate commercial servers.