>In my shop, that would bring ADSM to its knees, since I set up all of
>the automation using my id.

I think the obvious solution here is to simply define a general administrative
ID within a shop (much like root on a Unix system) and use that for
administrative tasks involving configuration changes where ADSM is sensitive
to the administrator ID.  Use private administrator IDs for queries, Set
commands, and the like.  Individual administrators can then come and go, but
the general one can persist.
     Richard Sims, Boston University OIT