Deploying to gh-pages from @ 567000a 🚀

_preview/203/_sources/guides/team_guide.md

@@ -103,7 +103,7 @@ This section describes admin tasks that are necessary for the maintenance of LEA
 
 ### Member Sign Up Troubleshooting
 
-Ideally members should be signed on automatically and well ahead of any event. But despite the best efforts situations arise where either staff or the organizers/instructors of an event need to quickly sign on new members, and troubleshoot if certain users do not have access to the JupyterHub. Follow the steps in this Flowchart to quickly resolve any issues in such cases.
+Ideally members should be signed on automatically and well ahead of any event (see [](reference.member_sign_up) for an overview of our member sign up mechanics). But despite the best efforts situations arise where either staff or the organizers/instructors of an event need to quickly sign on new members, and troubleshoot if certain users do not have access to the JupyterHub. Follow the steps in this Flowchart to quickly resolve any issues in such cases.
 
 ![](../images/member_troubleshooting.png)
 

_preview/203/_sources/reference/membership.md

@@ -63,3 +63,13 @@ Removing a user from the `leap-pangeo-users` group entirely will disable their a
 completely.
 An automated process will delete user data from the hub one month after a user
 is removed from the `leap-pangeo-users` group.
+
+(reference.member_sign_up)=
+
+## Member Sign Up Procedure
+
+![](../images/member_sign_up_schematic.png)
+
+All data relevant to LEAP membership is centrally processed in a spreadsheet with access limited to LEAP staff. To allow LEAP members access to the JupyterHub (and the associated storage and compute resources; all managed by 2i2c) the [](support.data_compute_team) maintains a set of Github Actions that parse the relevant data like github usernames and membership expiration, and add users to the appropriate [teams](reference.membership.team-resources).
+For normal operations users should [apply](users.membership.apply) and wait a few days until they are approved, entered, and signed up for access.
+For urgent situations (like events, classes) that require expedited sign up please refer to [](guide.team.admin.member_signup_troubleshooting).

_preview/203/guides/team_guide.html

@@ -769,7 +769,7 @@ <h2>Non-Technical Admin Tasks<a class="headerlink" href="#non-technical-admin-ta
 <p>This section describes admin tasks that are necessary for the maintenance of LEAP-Pangeo components (including collaborative efforts lead M²LInES) which require appropriate permissions, but no coding (everything can be achieved on one of several websites).</p>
 <div class="section" id="member-sign-up-troubleshooting">
 <span id="guide-team-admin-member-signup-troubleshooting"></span><h3>Member Sign Up Troubleshooting<a class="headerlink" href="#member-sign-up-troubleshooting" title="Permalink to this headline">¶</a></h3>
-<p>Ideally members should be signed on automatically and well ahead of any event. But despite the best efforts situations arise where either staff or the organizers/instructors of an event need to quickly sign on new members, and troubleshoot if certain users do not have access to the JupyterHub. Follow the steps in this Flowchart to quickly resolve any issues in such cases.</p>
+<p>Ideally members should be signed on automatically and well ahead of any event (see <a class="reference internal" href="../reference/membership.html#reference-member-sign-up"><span class="std std-ref">Member Sign Up Procedure</span></a> for an overview of our member sign up mechanics). But despite the best efforts situations arise where either staff or the organizers/instructors of an event need to quickly sign on new members, and troubleshoot if certain users do not have access to the JupyterHub. Follow the steps in this Flowchart to quickly resolve any issues in such cases.</p>
 <p><img alt="" src="../_images/member_troubleshooting.png" /></p>
 <div class="section" id="a-g-check-if-a-user-is-in-the-member-spreadsheet">
 <h4>A+G: Check if a user is in the Member Spreadsheet<a class="headerlink" href="#a-g-check-if-a-user-is-in-the-member-spreadsheet" title="Permalink to this headline">¶</a></h4>

_preview/203/reference/membership.html

@@ -358,6 +358,11 @@ <h1 class="site-logo" id="site-title">Technical Documentation</h1>
    Offboarding Process
   </a>
  </li>
+ <li class="toc-h2 nav-item toc-entry">
+  <a class="reference internal nav-link" href="#member-sign-up-procedure">
+   Member Sign Up Procedure
+  </a>
+ </li>
 </ul>
 
             </nav>
@@ -415,6 +420,11 @@ <h2> Contents </h2>
    Offboarding Process
   </a>
  </li>
+ <li class="toc-h2 nav-item toc-entry">
+  <a class="reference internal nav-link" href="#member-sign-up-procedure">
+   Member Sign Up Procedure
+  </a>
+ </li>
 </ul>
 
                         </nav>
@@ -504,6 +514,13 @@ <h2>Offboarding Process<a class="headerlink" href="#offboarding-process" title="
 An automated process will delete user data from the hub one month after a user
 is removed from the <code class="docutils literal notranslate"><span class="pre">leap-pangeo-users</span></code> group.</p>
 </div>
+<div class="section" id="member-sign-up-procedure">
+<span id="reference-member-sign-up"></span><h2>Member Sign Up Procedure<a class="headerlink" href="#member-sign-up-procedure" title="Permalink to this headline">¶</a></h2>
+<p><img alt="" src="../_images/member_sign_up_schematic.png" /></p>
+<p>All data relevant to LEAP membership is centrally processed in a spreadsheet with access limited to LEAP staff. To allow LEAP members access to the JupyterHub (and the associated storage and compute resources; all managed by 2i2c) the <a class="reference internal" href="../support.html#support-data-compute-team"><span class="std std-ref">Data and Computation Team</span></a> maintains a set of Github Actions that parse the relevant data like github usernames and membership expiration, and add users to the appropriate <a class="reference internal" href="#reference-membership-team-resources"><span class="std std-ref">teams</span></a>.
+For normal operations users should <a class="reference internal" href="#users-membership-apply"><span class="std std-ref">apply</span></a> and wait a few days until they are approved, entered, and signed up for access.
+For urgent situations (like events, classes) that require expedited sign up please refer to <a class="reference internal" href="../guides/team_guide.html#guide-team-admin-member-signup-troubleshooting"><span class="std std-ref">Member Sign Up Troubleshooting</span></a>.</p>
+</div>
 </div>
 
     <script type="text/x-thebe-config">