---
title: 01. Onboarding
---

**ESTABLISHING ONBOARDING PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

## 1. INTRODUCTION AND LEGAL FRAMEWORK

### 1.1. Policy Overview

This Onboarding Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for participants accepted into our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.

### 1.2. Scope and Applicability

This Documentation applies to all individuals who have been accepted into our Mentorship Programme. All participants must complete the onboarding procedures set forth in this Documentation to gain full programme access.

**IMPORTANT: This is a self-guided programme. Once you complete onboarding, you can work through the programme documentation at your own pace. Reviews and approvals are optional and available upon request. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**

## 2. APPLICATION ACCEPTANCE AND CONFIRMATION

### 2.1. Acceptance Notification

Upon review and acceptance of your application, you will receive an email confirmation of your acceptance into the Mentorship Programme.

### 2.2. Required Response

**Mandatory Requirement:** You MUST reply to the acceptance confirmation email with your GitHub username.

**Consequences of Non-Compliance:**
- Failure to respond with your GitHub username will prevent completion of onboarding procedures
- Programme access cannot be granted without GitHub account information
- Programme acceptance may be withdrawn if required information is not provided within reasonable timeframes

## 3. DISCORD COMMUNITY ACCESS

### 3.1. Discord Community Requirement

All programme participants must join our [Discord community](https://chat.nhcarrigan.com/) to access programme resources, communications, and support.

### 3.2. Discord Community Purpose

The Discord community serves as the primary platform for:
- Programme planning and coordination
- Coaching sessions and mentorship activities
- Participant communication and collaboration
- Resource sharing and programme announcements

### 3.3. Role Assignment Procedures

**Self-Selectable Role Process:**
1. Join the Discord community using the provided invitation link
2. Navigate to the Channels and Roles section
3. Select the mentorship role from the available self-selectable roles
4. The mentorship role will be automatically assigned and provides access to programme-specific channels and resources

## 4. GITHUB REPOSITORY ACCESS

### 4.1. Repository Purpose and Restrictions

**Repository Usage Limitations:**

**IMPORTANT: The repository provided to programme participants is designated EXCLUSIVELY for flagship project development. The following restrictions apply:**

- **Prohibited Content:** Participants must NOT commit practice projects, LeetCode solutions, or any code unrelated to the flagship project
- **Resume Portfolio:** This repository will be listed on resumes for job applications
- **Quality Standards:** Only high-quality, professional code appropriate for portfolio presentation should be committed
- **Violation Consequences:** Violation of repository usage restrictions may result in disciplinary action, including potential programme expulsion

### 4.2. Repository Invitation and Acceptance

**Invitation Process:**
- Programme participants will receive an invitation to a dedicated repository under our organisation
- The repository is designated for flagship project code storage and development
- Participants must accept the repository invitation within seven (7) days of receipt
- Invitations that are not accepted within seven (7) days will expire and may require re-invitation

### 4.3. Repository Access and Permissions

**Access Level:**
- Participants receive maintainer-level access to their designated repository
- Maintainer access permits configuration of repository settings, including:
  - Workflow configurations
  - Branch protection rules
  - Repository settings and preferences

**Access Restrictions:**
- Participants do not have access to destructive repository settings
- Certain administrative functions remain restricted to organisation administrators
- Access levels are designed to balance participant autonomy with organisational security

## 5. ONBOARDING COMPLETION

### 5.1. Completion Requirements

Onboarding is considered complete when:
- Acceptance confirmation email has been responded to with GitHub username
- Discord community membership has been established
- Mentorship role has been assigned in Discord
- GitHub repository invitation has been accepted
- All required information has been provided to programme leadership

### 5.2. Programme Access

Upon completion of onboarding procedures, participants gain full access to:
- Programme-specific Discord channels
- GitHub repository for flagship project development
- Programme resources and documentation (self-guided guides 01-10)
- Resource library with templates, examples, and checklists
- On-demand support from programme leadership and community members

## 6. LIMITATION OF LIABILITY AND DISCLAIMERS

### 6.1. Reference to Comprehensive Liability Framework

**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**

### 6.2. Onboarding Disclaimer

This Documentation establishes mandatory onboarding procedures. However:

- Programme leadership reserves the right to modify onboarding procedures at any time
- Once onboarding is complete, the programme is self-guided and participants work at their own pace
- Reviews and approvals are optional and available upon request
- Programme leadership is not responsible for technical issues preventing onboarding completion beyond our reasonable control

## 7. CONCLUSION

This Onboarding Documentation establishes the procedures and requirements for participants accepted into our Mentorship Programme. All participants must complete these procedures to gain full programme access.

Questions about onboarding procedures should be directed to programme leadership through designated communication channels. For comprehensive programme terms and conditions, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).

---

*For questions about onboarding procedures or programme participation, please contact programme leadership through the designated channels outlined in our Community Code of Conduct.*

:::tip[Helpful Links]
- [Join Discord](https://chat.nhcarrigan.com/) - Select the mentorship role to get started
- [Donate](https://donate.nhcarrigan.com/)
:::