Add link to NMFS workshop registry

password-access.qmd

@@ -17,8 +17,8 @@ and participants, Hub admins do not have any way to contact the people added to
 the Hub. Thus, participants with this method are only allowed to stay in the Hub
 for one week before being removed.
 
-1. Open an issue in the appropriate `workshop-planning` repository ([NASA](https://github.com/nasa-openscapes/workshop-planning/issues)/NOAA [TBD]) outling your workshop. 
-Also add it to the [workshop registry](https://docs.google.com/spreadsheets/d/1Sg4fMDGxMLI0p5cgK5xyamFJpKC6NyNneqXLDReSKcg/edit#gid=695033382), and 
+1. Open an issue in the appropriate `workshop-planning` repository ([NASA](https://github.com/nasa-openscapes/workshop-planning/issues)/NMFS [TBD]) outling your workshop. 
+Also add it to the workshop registry ([NASA](https://docs.google.com/spreadsheets/d/1Sg4fMDGxMLI0p5cgK5xyamFJpKC6NyNneqXLDReSKcg/edit#gid=695033382)/[NMFS](https://docs.google.com/spreadsheets/d/14GDUFU3_H2bZcSt--VGLRmrRFq3dylDL8ZeAKuFbV6E/edit?gid=695033382#gid=695033382)), and 
 put "SinglePassword" in the `2i2c access type` column. 
 If you don't have access to this sheet, reach out to the [primary contact/admin for your hub](about.qmd#primary-contacts).
 2. Check with the [primary contact/admin](about.qmd#primary-contacts) to ensure that the Hub image has the packages you need.
@@ -89,9 +89,9 @@ and users' home directories be removed *from the workshop hub*.
 *This section is for [Hub admins](about.qmd#primary-contacts) (Openscapes core team plus NASA/NOAA hub leads), who have access to the [SharedPasswords-Openscapes.Cloud Google Sheet](https://docs.google.com/spreadsheets/d/1Y4qzqWLsKHTNzuQi-fOaHGud0Ld_q1GHAzhS9-grV7Q/edit?gid=0#gid=0), and have close working relationships with 2i2c. 
 These steps intentionally align with the steps outlined above for workshop leads, and are meant to be collaborative - experienced mentors will be more familiar with the process and need less help than people leading workshops using the hub for the first time.*
 
-1. Work with workshop lead to open an issue in the appropriate `workshop-planning` repository ([NASA](https://github.com/nasa-openscapes/workshop-planning/issues)/NOAA [TBD]), and add it to the MainPlanning project board ([example](https://github.com/orgs/NASA-Openscapes/projects/7/views/1?pane=issue&itemId=93334218&issue=NASA-Openscapes%7Cworkshop-planning%7C137)).
+1. Work with workshop lead to open an issue in the appropriate `workshop-planning` repository ([NASA](https://github.com/nasa-openscapes/workshop-planning/issues)/NMFS [TBD]), and add it to the MainPlanning project board ([example](https://github.com/orgs/NASA-Openscapes/projects/7/views/1?pane=issue&itemId=93334218&issue=NASA-Openscapes%7Cworkshop-planning%7C137)).
 
-2. Record the workshop in the [workshop registry](https://docs.google.com/spreadsheets/d/1Sg4fMDGxMLI0p5cgK5xyamFJpKC6NyNneqXLDReSKcg/edit#gid=695033382), and put "SinglePassword" in the `2i2c access type` column in the appropriate row. All mentors should also have access to this sheet.
+2. Record the workshop in the workshop registry ([NASA](https://docs.google.com/spreadsheets/d/1Sg4fMDGxMLI0p5cgK5xyamFJpKC6NyNneqXLDReSKcg/edit#gid=695033382)/[NMFS](https://docs.google.com/spreadsheets/d/14GDUFU3_H2bZcSt--VGLRmrRFq3dylDL8ZeAKuFbV6E/edit?gid=695033382#gid=695033382)), and put "SinglePassword" in the `2i2c access type` column in the appropriate row. All mentors should also have access to this sheet.
 
 3. Help the workshop lead ensure that the resources in the hub are sufficient for the workshop's needs. 
 The default configuration should easily handle up to 100 particpants; more than that may require some work by 2i2c to scale up.