Fulfillment Guide

1. You are here:
2. Handbook
3. Product Handbook
4. Fulfillment Guide

On this page

• Overview
• Customer subscription lifecycle
  • Current processes
    • Trial
    • New
    • Additional seat purchase
    • Renewal
    • Cancelation
  • License Expiration
  • Future iterations
• CustomersDot Admin Panel
  • Searching
  • Account
    • Adding another account to manage subscription
    • GitLab Groups
  • Trials
    • Check, change, or extend trial expiry date
• How to connect with us
• Links

Overview

The Fulfillment Sub-department is responsible for the infrastructure between the systems which affect the user purchasing process, as well as being the primary caretakers of the CustomersDot](/handbook/engineering/development/fulfillment/#customersdot) system.

We frequently collaborate with other teams. For example if we are making a change which will affect usage ping we collaborate with the Product Intelligence group. When our work involves or affects any backend enterprise application, we collaborate with the Sales Systems team.

Customer subscription lifecycle

Customers interact with GitLab throughout the trial and purchasing journey in a variety of ways. This section will capture that journey, which will evolve over time.

Current processes

Trial

• SaaS subscription purchase, documented by UX
• Self-managed subscription purchase, documented by UX
• Trial flow, documented by EntApps team

New

• SaaS subscription purchase, documented by UX
• Self-managed subscription purchase, documented by UX
• New business flow, documented by EntApps team

Additional seat purchase

• SaaS subscription purchase, documented by UX
• Self-managed subscription purchase, documented by UX

Renewal

• SaaS subscription purchase, documented by UX
• Self-managed subscription purchase, documented by UX
• Renewal Emails, documented by UX
• Renewal notifications, documented by EntApps team
• Renewal system flow, documented by EntApps team

Cancelation

• UX flow documentation

License Expiration

• What happens when the license expires
• Process for extending licenses during renewal, trial extensions, etc
• Internal process for creating a trial license (for extension)

Future iterations

We will be making updates to the current processes as the business needs evolve, and we learn from our customers' experiences. Here are some new projects that we are looking forward to:

1. Updates to renewal customer messaging
2. Quarterly co-terms
3. Auto-renewals

CustomersDot Admin Panel

The target audience is the internal GitLab team, and covers the admin panel of the CustomersDot. Customers or subscription managers should refer to the Customers section of GitLab's user documentation for help in using the portal, or the licensing FAQ for questions on subscriptions such as how users are counted.

Searching

When using the admin panel search, be aware that results will be based on searching only one field at a time. For example, entering a person's full name will likely provide no results because the system will not search first and last name at the same time, only one or the other.

We recommend searching by email address, partial email address (e.g. company domain), or company name. When searching by name, enter only first or last name.

Account

Adding another account to manage subscription

1. Find existing customer and click on Edit.
2. Copy the Zuora and SFDC IDs.
3. Paste the IDs into the same fields for the requesting customer.

GitLab Groups

If an account has a connected GitLab.com user account, then a list of namespaces will show with relevant information including current plan.

The list of namespaces are:

• personal namespace
• top level group namespaces where user is Owner

Trials

Check, change, or extend trial expiry date

Note: Until customers #973 and customers #1643 are resolved, this is unlikely to be available.

1. Find the customer who initiated the trial.
2. Click on the GitLab Groups.
3. If the trial is expired and needs to be extended, click on the Renew Trial button.
4. Change the trial date as necessary and click on Update. Warning: Do not change the date to a date prior to today's date in UTC timezone.

How to connect with us

• For help with a license error, resending a license or other support requests, create an internal issue for the support team.
• For general product questions, try the #Questions Slack channel.
• Reach out to #s_fulfillment with non-customer specific purchasing or provisioning questions, or to escalate an outage in our purchasing workflow.
• To raise awareness or request elevated priority of an issue, mention @amandarueda in the issue and provide relevant information.

Links

To be added