diff --git a/how-to/manage-users.rst b/how-to/manage-users.rst
index 3442d10..96f35c8 100644
--- a/how-to/manage-users.rst
+++ b/how-to/manage-users.rst
@@ -39,19 +39,26 @@ For staging and qastaging we should:
 user by running ``sudo -iu stg-launchpad``. 
 
 2. SSH into the ``launchpad-admin`` juju unit, by running 
-``in-model qastaging juju ssh launchpad-scripts/leader``.
+``in-model qastaging juju ssh launchpad-admin/leader``.
 
-3. Switch to ``launchpad`` user, by running 
-``sudo su launchpad``.
-
-4. Add the user to the team by running: 
+3. Add the user to the team by running: 
 
 .. code::
      
-     LPCONFIG=launchpad-admin /srv/launchpad/code/utilities/anoint-team-member <username> <team-name>
+     /srv/launchpad/code/utilities/anoint-team-member <username> <team-name>
 
 In our example:
 
 .. code::
      
-     LPCONFIG=launchpad-admin /srv/launchpad/code/utilities/anoint-team-member test-user admins
+     /srv/launchpad/code/utilities/anoint-team-member test-user admins
+
+.. note::
+
+    Note that for running some of these scripts, it is common to need to add a
+    ``LPCONFIG=launchpad-admin`` at the start of the command to set the needed
+    environmental variable. This is not necessary here because it is already
+    set in the environment within the ``launchpad-admin`` unit.
+    Running this command in another unit (for example, ``launchpad-scripts``)
+    would require running as ``LPCONFIG=launchpad-admin
+    /srv/launchpad/code/utilities/anoint-team-member <username> <team-name>``.