diff --git a/sphinx/index.rst b/sphinx/index.rst
index 997d540..926b38a 100644
--- a/sphinx/index.rst
+++ b/sphinx/index.rst
@@ -1,6 +1,12 @@
 Welcome to Specify Developer documentation!
 ===========================================================
 
+.. toctree::
+   :maxdepth: 1
+   :caption: Specify:
+
+   specify/adding_new_levels
+
 .. toctree::
    :maxdepth: 1
    :caption: Amazon Web Services:
diff --git a/sphinx/specify/adding_new_levels.md b/sphinx/specify/adding_new_levels.md
new file mode 100644
index 0000000..dadcf7e
--- /dev/null
+++ b/sphinx/specify/adding_new_levels.md
@@ -0,0 +1,56 @@
+# Steps After Adding a New Institutional Scoping Level in Specify 7
+
+_Last updated 2024-12-09_
+
+After adding a new [institutional scoping level](https://discourse.specifysoftware.org/t/specify-institutional-scopings/1046) (collection, discipline, division) to a Specify 7 database, follow these steps:
+
+![Example hierarchy](https://global.discourse-cdn.com/flex029/uploads/specifysoftware/original/2X/d/d48c17f6c1a95289032a45963388ee499f20f889.jpeg)
+
+![Scoping hierarchy](scopinghierarchy.png)
+
+> **WARNING:** Before following any of these steps, make sure to take a complete backup of any production database.
+
+## Collection
+
+_WIP_
+
+## Discipline
+
+### Uniqueness Rules
+
+**Problem:** When a new discipline is added, the uniqueness rules are not automatically applied. This occurs because the migration process that creates the uniqueness rules is not already complete and does not run again.
+
+> ⚠️ **Warning:** Make sure to note any custom uniqueness rules. If any do not match the system's defaults, carefully back them up and re-add them once these steps are complete.
+
+
+**Solution:** 
+
+1. Drop the `uniquenessrule_fields` table.
+2. Drop the `uniquenessrule` table.
+3. Remove the Django migration records associated with these migrations:
+
+    ```sql
+    delete from django_migrations where name IN ('0001_initial','0002_default_unique_rules');
+    ```
+
+4. Enter the container directly via command line:
+
+    ```bash
+    docker exec -it specifycloud-example-1 /bin/bash
+    ```
+
+    Inside the Docker `specify7` container, re-run the migrations:
+    ```bash
+    ve/bin/python manage.py migrate businessrules 0002_default_unique_rules
+    ```
+
+5. Verify that the `uniquenessrule_fields` and `uniquenessrule` tables are present. Go to the Schema Config in each discipline and verify that 'Collection Object' has a uniqueness rule for catalog number.
+
+
+## Division
+
+_WIP_
+
+## Institution
+
+You may only have one institution per Specify database at this time.
\ No newline at end of file
diff --git a/sphinx/specify/scopinghierarchy.png b/sphinx/specify/scopinghierarchy.png
new file mode 100644
index 0000000..9195dd7
Binary files /dev/null and b/sphinx/specify/scopinghierarchy.png differ