Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Generating GitLab Team Member Licenses

  1. You are here:
  2. Handbook
  3. Support Team Handbook
  4. Support Operations Team
  5. Support Operations Workflows
  6. Generating GitLab Team Member Licenses

Overview

Process

  1. The GitLab team member files an access request (AR) using the GitLab Team Member License request template.
  2. GitLab team member pings Support Ops.
  3. Support Operations reviews the AR to ensure it meets the acceptable parameters.
    1. If it does not, review the reason it goes outside the acceptable parameters. If this is valid, proceed. If not, communicate via the issue that the reason is not sufficient.
  4. Support Operations logs into the CustomersDot app and generates the license using the parameters in the AR.
  5. Support Operations updates the AR and closes it out.

Flowchart

graph TD; A-->B; B-->C; C-->D; D--Yes-->E; E-->F; D--No-->H; F--Yes-->H; F--No-->G; H-->I; A(GitLab team member opens an AR issue) B(GitLab team member ping Support Ops) C(Support Ops reviews the AR) D(Does the request go outside acceptable parameters?) E(Support Ops reviews the reason) F(Is the reason acceptable?) G(Support Ops communicates why it is not acceptable and denies the request) H(Support Ops creates the license) I(Support Ops updates and closes the AR)

Acceptable parameters

Anything deviating from the above will require a reason and approve from a Support Operations Manager.

Creating a license

  1. Login to the license app.
  2. Click the green New license button on the right hand side.

  3. Fill out the fields using the below table:

    Field Value Exceptions possible?
    Name GitLab team member's full name No
    Company GitLab - Team Member License No
    Email GitLab team member's company email No
    Zuora subscription ID leave this blank No
    Zuora subscription name leave this blank No
    Users count 100 Yes, with support ops managers approval
    Previous users count 0 or value from the AR No
    Trueup count 0 or value from the AR No
    Plan code value from the AR No
    Trial leave unchecked No
    Start date today's date No
    End date 1 year from today Yes, with support ops managers approval
    Notes the AR link No
  4. Click the blue Save button.
  5. From there, locate the license on the CustomersDot license list page and copy the entire License key section.
  6. Update the Access Request letting them know you generated them the license key and they have received an email from renewals@gitlab.com.
  7. Close out the issue.

Applying the license

For info on applying licenses, please see https://docs.gitlab.com/ee/user/admin_area/license.html#activate-gitlab-ee-with-a-license-file

Open in Web IDE View source