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.
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.
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:
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.
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.
After your initial search, you can further filter the search results.
In the search results, any account which has a subscription tied to it will have a "Subscription" badge next to their name.
To edit an account's details, such as name.
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:
Update. Warning: Do not change the date to a date prior to today's date in UTC timezone.
To be added