diff --git a/docs/63_dandi_infrastructure.md b/docs/63_dandi_infrastructure.md
index 104537e3..2ce79b48 100644
--- a/docs/63_dandi_infrastructure.md
+++ b/docs/63_dandi_infrastructure.md
@@ -2,4 +2,6 @@
## Configuring Terraform
-## Manual Steps in the AWS Console and Netlify
\ No newline at end of file
+## Manual Steps in the AWS Console and Netlify
+
+## Setting up Email
\ No newline at end of file
diff --git a/docs/64_dandi_archive.md b/docs/64_dandi_archive.md
index d09e00c2..0ad47486 100644
--- a/docs/64_dandi_archive.md
+++ b/docs/64_dandi_archive.md
@@ -120,6 +120,28 @@ class HerokuProductionConfiguration(DandiMixin, HerokuProductionBaseConfiguratio
## Approval of Users
+By default in DANDI, only users whose emails end in `.edu` are automatically approved -- [for code reference, see here](https://github.com/dandi/dandi-archive/blob/6e72653688a6b45066c04b94a44f830b734887dd/dandiapi/api/views/auth.py#L127).
+For all other users, proceed into the Django Admin panel.
+
+Click on the `Users` tab -- in the tab, find the appropriate user and click on their e-mail
+
+
+![]()
+
+
+Scroll down to the `User Metadata` section, where you will see a `Status` option.
+
+Click `Approved` and then `Save` on the bottom of the screen -- the user will now have access to a valid API Key, in which they can interact with relevant assets within your Archive
+
+
+![]()
+
## Setting up Staging Environments
\ No newline at end of file
diff --git a/docs/img/user_approval.png b/docs/img/user_approval.png
new file mode 100644
index 00000000..33ef5e2a
Binary files /dev/null and b/docs/img/user_approval.png differ
diff --git a/docs/img/user_metadata.png b/docs/img/user_metadata.png
new file mode 100644
index 00000000..496611f6
Binary files /dev/null and b/docs/img/user_metadata.png differ