During 2021, we are working on automation projects for the Community Programs Applications Workflow. This page is a work in progress as we document the workflow and troubleshoot the process.
This page describes the automated workflows for the following community programs:
|Community Program||Handbook Page||Website||Program Owner|
|GitLab for Education||EDU Handbook||EDU website||Christina Hupy|
|GitLab for Open Source||OSS Handbook||OSS Website||Nuritzi Sanchez|
|GitLab for Startups||Startups Handbook||GitLab for Startups||Nuritzi Sanchez|
The goals of this page are to:
|0. Application||SheerId hosted application form is filled out for OSS and EDU. YC applicants fill out Marketo Form.|
|1. Verification||Automated verification by SheerID for EDU. Document review for OSS. Manual verification for YC.|
|2. Booking||Success email directs applicant to a separate Community Programs Self-Checkout page for each program on the GitLab Customer Portal. Coupon code is entered during checkout.|
|3. Provisioning||Licenses are provisioned through the web direct process on the GitLab Customer Portal.|
|4. Compliance||Handled by Sales-Support and Billing Ops.|
|5. Renewal||Program members will repeat the process within 3-months of renewal.|
|6. Support||Each step of the automated application workflow has different set of potential errors and support flow.|
GitLab uses a third party vendor, SheerID, for verification services. SheerId builds and hosts the application forms for the GitLab for Education Program and the GitLab for Open Source Program. All communications (email and browser notifications) sent during the verification phase for these two programs are hosted and sent by SheerID.
The DRI for SheerID is Christina Hupy. The contract is renewed on an annual basis and is based on the total number of verifications across the two programs.
MySheerID is the customer portal for the verification system. The portal contains details on each application form, a reporting system, and account settings. Anyone needing to access the MySheerId portal can request an account through an access request.
SheerID Customer Service specific to GitLab can be found here.
The verification process differs by program. The verification process for each program can be found on the pages below:
Once an applicant has submitted the requested fields on the form, the application processing team will be able to find all of the application information in Document Review on the MySheerID customer portal.
Only people who have been added to the MySheerID customer portal have access to Document Review.
Below are instructions for how the application processing team can review applications for the GitLab for Open Source program or escalated cases for the GitLab for Education program.
How to begin reviewing:
Beginin the upper left hand corner (Make sure to adjust the filter to chronological order to make sure to address the users who have been waiting the longest).
Does the affiliation type on the document match a qualified open source project? (FIXME: Need to figure out if this is needed for OSS)
Make sure you have selected an affiliation type otherwise you will not be able to approve the document. (FIXME: Need to figure out if this is needed for OSS)
If all of the above are true select
FIXME: Add information on what to do if it needs to be rejected. Do the above instructions work for both qualifying and non-qualifying applications?
If there is a discrepancy regarding the legitimacy of the document and or the application requires help from another team member, navigate to the comments section at the bottom of the page.
Commentand describe the issue as clear as possible
Escalateto tag a team member and place the application in the escalation queue
The links below contain helpful resources when navigating the SheerID review portal.
Upon successful verification, the applicant will receive an email with instructions to obtain their license and a unique coupon code.
Coupon codes are provided to SheerID by Christina Hupy via an email to email@example.com. The coupon codes are provided in an individual .csv for each program. The .csv should only have one column with no header. Enough coupon codes to cover one year of verifications for each program will be provided at a time. The number of coupon codes per year is determined by estimated the number of applications expected per quarter + the number of expected renewals * an average re-verification factor.
The success email will contain a direct link to a program specific Self-Checkout page for each of the three programs (EDU/OSS/YC) in the GitLab Customer Portal. The program specific Self-Checkout pages are not available directly in the GitLab Customer Portal without the direct link. The applicant will need to enter the unique coupon code during the Self-Checkout process. The handbook for the Custom Self-Checkout flow on the GitLab Customer Portal is here [TBD].
During the Self-Checkout process, the applicant will need to accept terms specific to the relevant program: GitLab for Education Program Agreement or GitLab for Open Source Agreement. The GitLab for Startups Terms are presented directly upon checkout.
The GitLab for Startups Terms:
If you meet the requirements of the Start-Up Program, you will be eligible for ONE (1) of the following Options:
Option 1: Receive twelve (12) months Ultimate [SaaS or Self-Managed] at no cost, without Support. Option 2: Receive twelve (12) months Ultimate [SaaS or Self-Managed] with Support, for $59.40(USD) per User (per Year). Both options are available for ONE (1) TIME use, and only for ONE (1) YEAR. Renewal of the User(s) will be at the current published List Price.
Your use of the GitLab Software is subject to the GitLab Subscription Agreement. For Option 1, the Software is provided as “Free Software”.
Licenses will be provisioned directly during Self-checkout process via the WebDirect flow.
Compliance is handled by Sales-Support and Billing Ops. This phase results in granting the license and notifying the customer of how to access the licenses.
The renewal phase of the Community Efficiency Project is currently in the scoping stage and work is expected to be completed in the 14.1 milestone for the fulfillment team beginning 2021-07-21. This work will add the ability to renew license upon successful verification directly in the GitLab Customers Portal via the program specific Self-Checkout page.
Until the renewal phase is completed, the renewal process will remain as stated on the Community Programs Applications Workflow page.
Each step of the automated application workflow has different set of potential errors and support flow.
|Verification||SheerID Application||False Rejection EDU||SheerID||Contact SheerID from Rejection Email.|
|Verification||SheerID Application||False Rejection OSS||@nuritzi / OSS Program||Contact firstname.lastname@example.org from rejection email|
|Verification||SheerID Application||Never received success email.||SheerId||SheerId Help Center FAQ - Form resends email|
|Verification||SheerID Application||Deletes success email.||SheerId||SheerId Help Center FAQ - Form resends email|
|Verification||SheerID Application||Form not responding or something goes wrong with form.||SheerID||Contact SheerID Support Team|
|Verification||SheerID Application||Applicant makes a case to SheerID that EDU rejection was in error but SheerID cannot resolve.||@c_hupy||SheerID emails email@example.com with details. GitLab EDU team resolves.|
|Booking||GitLab Customer Portal||Coupon Code has already been used.||GitLab Support||Error message on the portal.
|Booking||GitLab Customer Portal||Coupon Code is invalid.||GitLab Support||Error message on the portal.
|Fulfillment||GitLab Customer Portal||Any problems with Customer Portal after coupon code succeeds.||GitLab Support||Open Support Ticket