diff --git a/docs/developer/README.md b/docs/developer/README.md
index 464626b87..dd7fc7737 100644
--- a/docs/developer/README.md
+++ b/docs/developer/README.md
@@ -84,7 +84,7 @@ While on production (the sandbox referred to as `stable`), an existing analyst o
 
  To get access to /admin on every non-production sandbox and to use /admin in local development, do the following:
 
-1. Login via login.gov
+1. Login to a sandbox environment (like staging at https://getgov-staging.app.cloud.gov/) via identity sandbox login.gov
 2. Go to the home page and make sure you can see the part where you can submit a domain request
 3. Go to /admin and it will tell you that your UUID is not authorized (it shows a very long string, this is your UUID). Copy that UUID for use in 4.
 4. (Designers) Message in #getgov-dev that you need access to admin as a `superuser` and send them this UUID along with your desired email address. Please see the "Adding an Analyst to /admin" section below to complete similiar steps if you also desire an `analyst` user account. Engineers will handle the remaining steps for designers, stop here.
@@ -109,7 +109,7 @@ While on production (the sandbox referred to as `stable`), an existing analyst o
 ### Adding an analyst-level user to /admin
 Analysts are a variant of the admin role with limited permissions. The process for adding an Analyst is much the same as adding an admin:
 
-1. Login via login.gov (if you already exist as an admin, you will need to create a separate login.gov account for this: i.e. first.last+1@email.com)
+1. Login to a sandbox environment (like staging at https://getgov-staging.app.cloud.gov/) via identity sandbox login.gov (if you already exist as an admin, you will need to create a separate login.gov account for this: i.e. first.last+1@email.com)
 2. Go to the home page and make sure you can see the part where you can submit a domain request
 3. Go to /admin and it will tell you that UUID is not authorized, copy that UUID for use in 4 (this will be a different UUID than the one obtained from creating an admin)
 4. (Designers) Message in #getgov-dev that you need access to admin as a `superuser` and send them this UUID along with your desired email address. Engineers will handle the remaining steps for designers, stop here.
diff --git a/src/registrar/fixtures/fixtures_users.py b/src/registrar/fixtures/fixtures_users.py
index fdaa1c135..03c883cf5 100644
--- a/src/registrar/fixtures/fixtures_users.py
+++ b/src/registrar/fixtures/fixtures_users.py
@@ -178,6 +178,13 @@ class UserFixture:
             "email": "jaxon.silva@cisa.dhs.gov",
             "title": "Designer",
         },
+        {
+            "username": "d579b8eb-16cf-4830-9341-70ecf227a644",
+            "first_name": "Kim",
+            "last_name": "Allen",
+            "email": "kim+dotgov@truss.works",
+            "title": "Farmer",
+        },
     ]
 
     STAFF = [
@@ -297,6 +304,12 @@ class UserFixture:
             "last_name": "Abbitt-Analyst",
             "email": "kaitlin.abbitt@gwe.cisa.dhs.gov",
         },
+        {
+            "username": "79b55374-f1a3-4e06-8614-41ba70050cd5",
+            "first_name": "Kim-Analyst",
+            "last_name": "Allen-Analyst",
+            "email": "kim+a@truss.works",
+        },
     ]
 
     # Additional emails to add to the AllowedEmail whitelist.