GitLab SaaS subscriptions work slightly differently to Self-managed licenses.
Unlike Self-managed licenses which grant equal access to features across an installation, GitLab SaaS subscriptions are applied to namespaces on GitLab SaaS (typically groups). Members of groups that have subscriptions applied to them will enjoy those features anywhere within the licensed namespace. For example, if
BigCorp has an Ultimate license, the sub-groups
BigCorp/Backend will each have access to Ultimate features and share a common pool of Shared Runner minutes.
Ownerin the group.
39Premium seats with start date of
2020-03-04and end date
2021-03-04. During the license period, the customer add more users to the system that incurs
112 Users over license/
True-up. If this is charged as True-up on SFDC, the new license will not include the extra users in the current term so the customer would end up with a license with
112true-up which cannot be uploaded to their system because they now have
39 + 112=
151billable users on the system.
Users over license/
True-ups, if not being dealt with at renewal, should be charged as
Add-on usersto the license as mentioned in Quarterly Self-Managed Seat Reconciliation & Billing .
The best way to assist a user or system admin on any new platform is to arm them with the resources they will need when questions arise. During the onboarding process after the sale, the user/admin will receive an email from GitLab with pertinent information about their subscription. Highlight this and encourage them to save it somewhere easily accessible. While many of the links below are included in the email, it would be helpful to review each of the following resources personally with the user/admin.
A few more best practices to ensure a smooth start
The Pricing page includes a "Frequently asked questions for GitLab SaaS" section that answers "What features do not apply to GitLab SaaS?" in detail. Here are some highlights: