Quick Links: | Overview | Request Access | Sign In and Onboarding | Request a Repository | Repository Access | Guidance | Troubleshooting |
Overview
GitHub Enterprise is an institutionally supported platform for faculty and staff at Chico State to manage and collaborate on code, scripts, and related digital materials.
- Available to faculty and staff only
- Not available for students at this time
- Access and permissions are managed through campus identity systems
This article outlines how to request access, what to expect during onboarding, and how repository access is assigned.
Request Access
To request access to GitHub Enterprise:
- Submit a Request for GitHub Enterprise Access.
- Select the Type of GitHub Request and complete any additional fields.
- Submit the request and wait for an update.
Sign In and Onboarding
After submitting your request:
- You will receive confirmation that your service request has been submitted and is under review.
- Once approved, you will receive an invitation email from GitHub with a link to join Chico State’s GitHub Enterprise organization.
- Select the link in the email. Sign in to GitHub using an existing account, or create a new account if needed.
- If you do not already have a GitHub account, create one using a non-Chico State email address.
- After accepting the invitation, you will be prompted to sign in using your campus credentials. This connects your GitHub account to Chico State’s identity system.
- After completing SSO authentication, you will have access to the GitHub Enterprise organization. You may not see any repositories initially. This is expected.
- Repository access is granted separately through:
- Team membership, or
- Direct assignment by a repository owner
Important Note: Your personal GitHub account CANNOT use a Chico State email address and be invited to the organization. If your GitHub account uses your Chico State email address, complete these steps before onboarding:
1. Log in to the GitHub account that uses your Chico State email address.
2. Go to Settings > Email and add a non-Chico State email address.
3. Set the non-Chico State email address as your primary email.
This is required so your account can be properly linked during the onboarding process.
Complete SSO Sign-In
After accepting the invitation:
- Your account will be added to Chico State’s GitHub Enterprise environment
- You may be prompted to sign in using campus credentials
- This process connects your GitHub account to Chico State’s authentication system
View Available Repositories
Once onboarding is complete:
- You will be able to sign in to GitHub Enterprise
- You may initially not see any repositories. This is expected.
Repository access is granted separately after onboarding is complete.
Request a Repository
Repository Information
Depending on the request type, users may be asked to provide:
- Repository name
- Repository visibility, such as Internal or Private
- Requested access level
- Repository owner or responsible team
- Associated Entra ID group, if known
- Business purpose or justification
This information helps requests be completed more efficiently and may reduce follow-up questions.
Repository Access
Access Levels
Repository access may be granted at different permission levels:
- Read – View repository contents only
- Triage – Manage issues and pull requests without modifying code
- Write – Contribute code and repository content
- Maintain – Manage repository settings and access configuration
The appropriate level depends on the repository and business need.
Team Assignment
- GitHub teams may be aligned with Entra ID groups.
- Team naming may align with associated Entra ID groups for consistency.
- Membership is managed through Entra ID groups, not directly in GitHub.
Access Flow
AD Group → GitHub Team → Repository Access
- Users are added to an AD group
- The group is synchronized with a GitHub team
- The team is granted access to a repository
This model ensures access is centrally managed and consistent with campus identity systems.
Get Repository Access
After you have GitHub access, request repository access by:
- Being added to the appropriate AD group, or
- Contacting the repository owner
You will not automatically have access to repositories unless access is assigned. Repository owners manage repository access by assigning teams. Team membership is managed through Entra ID groups.
Guidance
Use AD Groups
- Manage access through AD groups whenever possible
- Avoid assigning access directly to individuals
Follow Data Classification
- Follow campus data handling guidelines
Clean Up Access
- Request removal of access when no longer needed
- Request deletion of repositories that are no longer in use
This helps maintain a secure and manageable environment.
Troubleshooting
Invitation Email Not Received
- Check your spam or junk folder
- Confirm your request has been approved
- Submit a follow-up service request if needed
Unable to Accept Invitation
- Ensure you are signed into the correct GitHub account
- Try using a private or incognito browser window
No Repositories Visible
- This is expected after initial access
- Repository access must be granted separately
GitHub Account Email Issue
Your personal GitHub account should use a non-Chico State email address so it can be linked during onboarding.
Update your email in GitHub settings if needed.
Issues Signing In
- You may be prompted to authenticate using campus credentials
- Follow the Single Sign-On prompts
Still need help? Contact IT Support Services for further assistance.
Help us improve our Knowledge Base! Click Yes or No below, then let us know what worked — or what didn’t. Your feedback helps us improve our content and provide the best possible support.