This page contains details regarding the verification process for the GitLab for Education Program. GitLab uses a third party, SheerId, for verification services. The GitLab for Education Program provides SheerId with the program requirements and the SheerId platform is able to verify if an individual meets our requirements by matching applicant-provided data against authoritative data sources automatically. SheerID instantly confirms whether or not there is a match and either successfully verifies the applicant or rejects the applicant.
SheerID hosts two separate forms for the GitLab for Education Program due to differences in the reference the data set.
The University Teacher Program form is the form for all higher education institutions in 194 countries. Details on the country list can be found here. This form contains the following fields:
(*) Note: US Embargoed countries are not on the list. SheerID is not able to separate out the two different regions in Ukraine so we have asked them to remove Ukraine entirely from the list of countries. If someone from Ukraine does want to apply, they will need to contact us directly and we will determine if they qualify based on the region of origin.
Note: Additional details regarding the verification database limitations can be found here.
The K‒12 Teacher Program form is the form for all K-12 institutions in the United States. SheerID does not currently have the reference data for K-12 in other countries, therefore this verification form is limited to the United States.
This form contains the following fields:
GitLab currently does not have the legal and operational requirements in place to offer SaaS licenses to any institution that may have children under the age of 13. Therefore, the K-12 portion of the GitLab for Education Program is on hold until the requirements are in place.
The SheerId verification flow for the University Teacher Program Form and K-12 Teacher Program Form are detailed here in the SheerID Flows section of the SheerID Developer Center.
If applicants are not successful with the automated verification process, they will be prompted to upload a document that shows: full name and school name with a date in the current year. Acceptable examples include Teacher ID card with valid date and pay stub from within the last 60 days.
Applicants will have 3 attempts to upload a document providing verification of eligibility. SheerID will manually review these documents. Upon the third unsuccessful attempt, applicant will be rejected.
If SheerID is unable to determine the eligibility based on the document review, SheerID will forward the applicant's record to firstname.lastname@example.org. The GitLab for Education team will review the documentation and determine eligibility.
Any individual can apply through the form and verify up to 5 times per 365 days. This limit provides room for error and allows a single individual at an institution to apply for licenses on behalf of individual sub-units within the institution. For example, an information technology administrator may apply and hold the license for multiple colleges or departments on one campus.
This limit is determined by GitLab and set in the system by SheerID. It can be changed at any time.
The SheerID verification process for the EDU program can be simulated by following the directions in this issue.
Simulating the verification will allow GitLab team members to view the browser and email communications sent to applicants.