diff --git a/mentors-framework/onboarding.qmd b/mentors-framework/onboarding.qmd
index 607c4e3..9ff351d 100644
--- a/mentors-framework/onboarding.qmd
+++ b/mentors-framework/onboarding.qmd
@@ -226,6 +226,8 @@ This is evolving.
 
 For NASA, we started off by creating a **Google Group** so we could easily add mentors to Google Folders and Calendars. This hasn't worked perfectly because not everyone can use their work address to access Google things. We collect a second email address in the ParticipantsList spreadsheet, but if we use Google Groups we need to make sure that everyone's Google-access emails are included in the Google Group.
 
+After we create a new Google Group, Julie, as Google Workspace Administrator, must change the Group Access Type to Allow Members Outside Your Organization.
+
 We're also using GitHub Teams more, for 2i2c access and coordinating. Rather than a Google Group that is difficult to hand off in terms of managing, a GitHub Team might be the way to go. This will raise challenges for any private info (e.g. Carpentries code), but that could be handled in Slack.
 
 ### Create a GitHub Team with Mentors