diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-12-17 14:59:07 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-12-17 14:59:07 +0300 |
commit | 8b573c94895dc0ac0e1d9d59cf3e8745e8b539ca (patch) | |
tree | 544930fb309b30317ae9797a9683768705d664c4 /doc/subscriptions | |
parent | 4b1de649d0168371549608993deac953eb692019 (diff) |
Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42
Diffstat (limited to 'doc/subscriptions')
-rw-r--r-- | doc/subscriptions/gitlab_com/index.md | 119 | ||||
-rw-r--r-- | doc/subscriptions/index.md | 14 | ||||
-rw-r--r-- | doc/subscriptions/self_managed/index.md | 83 |
3 files changed, 126 insertions, 90 deletions
diff --git a/doc/subscriptions/gitlab_com/index.md b/doc/subscriptions/gitlab_com/index.md index a03c8e758de..7dd08da74f9 100644 --- a/doc/subscriptions/gitlab_com/index.md +++ b/doc/subscriptions/gitlab_com/index.md @@ -1,7 +1,7 @@ --- -stage: none -group: unassigned -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers +stage: fulfillment +group: fulfillment +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments type: index, reference --- @@ -11,7 +11,7 @@ GitLab.com is GitLab Inc.'s software-as-a-service offering. You don't need to install anything to use GitLab.com, you only need to [sign up](https://gitlab.com/users/sign_up) and start using GitLab straight away. -In this page we'll go through the details of your GitLab.com subscription. +This page reviews the details of your GitLab.com subscription. ## Choose a GitLab.com group or personal subscription @@ -20,10 +20,12 @@ On GitLab.com you can apply a subscription to either a group or a personal names When applied to: - A **group**, the group, all subgroups, and all projects under the selected - group on GitLab.com will have the features of the associated tier. GitLab recommends + group on GitLab.com contains the features of the associated tier. GitLab recommends choosing a group plan when managing an organization's projects and users. -- A **personal userspace**, all projects will have features with the - subscription applied, but as it's not a group, group features won't be available. +- A **personal userspace**, all projects contain features with the + subscription applied, but as it's not a group, group features aren't available. + +You can read more about [common misconceptions](https://about.gitlab.com/handbook/marketing/strategic-marketing/enablement/dotcom-subscriptions/#common-misconceptions) regarding a GitLab.com subscription to help avoid issues. ## Choose a GitLab.com tier @@ -34,19 +36,19 @@ at each tier, see the ## Choose the number of users -NOTE: **Note:** +NOTE: Applied only to groups. A GitLab.com subscription uses a concurrent (_seat_) model. You pay for a subscription according to the maximum number of users enabled at once. You can add and remove users during the subscription period, as long as the total users -at any given time is within your subscription count. +at any given time doesn't exceed the subscription count. Every occupied seat is counted in the subscription, with the following exception: - Members with Guest permissions on a Gold subscription. -TIP: **Tip:** +NOTE: To support the open source community and encourage the development of open source projects, GitLab grants access to **Gold** features for all GitLab.com **public** projects, regardless of the subscription. @@ -64,7 +66,7 @@ To subscribe to GitLab.com: [Customers Portal](https://customers.gitlab.com/). 1. Link your GitLab.com account with your Customers Portal account. Once a plan has been selected, if your account is not - already linked, you will be prompted to link your account with a + already linked, GitLab prompts you to link your account with a **Sign in to GitLab.com** button. 1. Select the namespace from the drop-down list to associate the subscription. 1. Proceed to checkout. @@ -81,12 +83,12 @@ To subscribe to GitLab.com: [Customers Portal](https://customers.gitlab.com/). 1. Link your GitLab.com account with your Customers Portal account. Once a plan has been selected, if your account is not - already linked, you will be prompted to link your account with a + already linked, GitLab prompts you to link your account with a **Sign in to GitLab.com** button. 1. Select the namespace from the drop-down list to associate the subscription. 1. Proceed to checkout. -TIP: **Tip:** +NOTE: You can also go to the [**My Account**](https://customers.gitlab.com/customers/edit) page to add or change the GitLab.com account link. @@ -97,9 +99,9 @@ to the **Billing** section of the relevant namespace: - **For individuals**: Visit the [billing page](https://gitlab.com/profile/billings) under your profile. -- **For groups**: From the group page (*not* from a project within the group), go to **Settings > Billing**. +- **For groups**: From the group page (*not* from a project in the group), go to **Settings > Billing**. - NOTE: **Note:** + NOTE: You must have Owner level [permissions](../../user/permissions.md) to view a group's billing page. The following table describes details of your subscription for groups: @@ -107,11 +109,12 @@ to the **Billing** section of the relevant namespace: | Field | Description | |-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| | **Seats in subscription** | If this is a paid plan, represents the number of seats you've paid to support in your group. | - | **Seats currently in use** | Number of active seats currently in use. | + | **Seats currently in use** | Number of seats in use. | | **Max seats used** | Highest number of seats you've used. If this exceeds the seats in subscription, you may owe an additional fee for the additional users. | - | **Seats owed** | If your maximum seats used exceeds the seats in your subscription, you'll owe an additional fee for the users you've added. | + | **Seats owed** | If your maximum seats used exceeds the seats in your subscription, you owe an additional fee for the users you've added. | | **Subscription start date** | Date your subscription started. If this is for a Free plan, is the date you transitioned off your group's paid plan. | - | **Subscription end date** | Date your current subscription will end. Does not apply to Free plans. | + | **Subscription end date** | Date your current subscription ends. Does not apply to Free plans. | + | **Billable users list** | List of users that belong to your group subscription. Does not apply to Free plans. | ## Renew your GitLab.com subscription @@ -129,15 +132,15 @@ log in and verify or update: - The invoice contact details on the **Account details** page. - The credit card on file on the **Payment Methods** page. -TIP: **Tip:** +NOTE: Contact our [support team](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293) if you need assistance accessing the Customers Portal or if you need to change the contact person who manages your subscription. It's important to regularly review your user accounts, because: -- A GitLab subscription is based on the number of users. You will pay more than - you should if you renew for too many users, while the renewal will fail if you +- A GitLab subscription is based on the number of users. You could pay more than + you should if you renew for too many users, while the renewal fails if you attempt to renew a subscription for too few users. - Stale user accounts can be a security risk. A regular review helps reduce this risk. @@ -146,7 +149,7 @@ It's important to regularly review your user accounts, because: A GitLab subscription is valid for a specific number of users. For details, see [Choose the number of users](#choose-the-number-of-users). -If the active user count exceeds the number included in the subscription, known +If the number of [billable users](#view-your-gitlabcom-subscription) exceeds the number included in the subscription, known as the number of _users over license_, you must pay for the excess number of users either before renewal, or at the time of renewal. This is also known the _true up_ process. @@ -172,8 +175,8 @@ previous period), log in to the [Customers Portal](https://customers.gitlab.com/ - If you see **Cancel subscription**, your subscription is set to automatically renew at the end of the subscription period. Click it to cancel automatic renewal. -With automatic renewal enabled, the subscription will automatically renew on the -expiration date and there will be no gap in available service. An invoice will be +With automatic renewal enabled, the subscription automatically renews on the +expiration date without a gap in available service. An invoice is generated for the renewal and available for viewing or download in the [View invoices](https://customers.gitlab.com/receipts) page. If you have difficulty during the renewal process, contact our @@ -193,10 +196,10 @@ To add users to a subscription: 1. Enter the number of additional users. 1. Select **Proceed to checkout**. 1. Review the **Subscription Upgrade Detail**. The system lists the total price for all users on the - system and a credit for what you've already paid. You will only be charged for the net change. + system and a credit for what you've already paid. You are only be charged for the net change. 1. Select **Confirm Upgrade**. -The following will be emailed to you: +The following is emailed to you: - A payment receipt. You can also access this information in the Customers Portal under [**View invoices**](https://customers.gitlab.com/receipts). @@ -215,6 +218,10 @@ To upgrade your [GitLab tier](https://about.gitlab.com/pricing/): When the purchase has been processed, you receive confirmation of your new subscription tier. +## See your billable users list + +To see a list of your billable users on your GitLab group page go to **Settings > Billing**. This page provides information about your subscription and occupied seats for your group which is the list of billable users for your particular group. + ## Subscription expiry When your subscription or trial expires, GitLab does not delete your data, but @@ -222,12 +229,12 @@ it may become inaccessible, depending on the tier at expiry. Some features may n behave as expected if you're not prepared for the expiry. For example, [environment specific variables not being passed](https://gitlab.com/gitlab-org/gitlab/-/issues/24759). -If you renew or upgrade, your data will again be accessible. +If you renew or upgrade, your data is accessible again. ## CI pipeline minutes CI pipeline minutes are the execution time for your -[pipelines](../../ci/pipelines/index.md) on GitLab's shared runners. Each +[pipelines](../../ci/pipelines/index.md) on GitLab shared runners. Each [GitLab.com tier](https://about.gitlab.com/pricing/) includes a monthly quota of CI pipeline minutes: @@ -258,19 +265,19 @@ Your own runners can still be used even if you reach your limits. ### Purchase additional CI minutes If you're using GitLab.com, you can purchase additional CI minutes so your -pipelines won't be blocked after you have used all your CI minutes from your +pipelines aren't blocked after you have used all your CI minutes from your main quota. You can find pricing for additional CI/CD minutes in the [GitLab Customers Portal](https://customers.gitlab.com/plans). Additional minutes: -- Are only used once the shared quota included in your subscription runs out. +- Are only used after the shared quota included in your subscription runs out. - Roll over month to month. To purchase additional minutes for your group on GitLab.com: 1. From your group, go to **Settings > Usage Quotas**. -1. Select **Buy additional minutes** and you will be directed to the Customers Portal. +1. Select **Buy additional minutes** and GitLab directs you to the Customers Portal. 1. Locate the subscription card that's linked to your group on GitLab.com, click **Buy more CI minutes**, and complete the details about the transaction. -1. Once we have processed your payment, the extra CI minutes will be synced to your group namespace. +1. Once we have processed your payment, the extra CI minutes are synced to your group namespace. 1. To confirm the available CI minutes, go to your group, then **Settings > Usage Quotas**. The **Additional minutes** displayed now includes the purchased additional CI minutes, plus any minutes rolled over from last month. @@ -278,8 +285,8 @@ To purchase additional minutes for your group on GitLab.com: To purchase additional minutes for your personal namespace: 1. Click your avatar, then go to **Settings > Usage Quotas**. -1. Select **Buy additional minutes** and you will be directed to the Customers Portal. -1. Locate the subscription card that's linked to your personal namespace on GitLab.com, click **Buy more CI minutes**, and complete the details about the transaction. Once we have processed your payment, the extra CI minutes will be synced to your personal namespace. +1. Select **Buy additional minutes** and GitLab redirects you to the Customers Portal. +1. Locate the subscription card that's linked to your personal namespace on GitLab.com, click **Buy more CI minutes**, and complete the details about the transaction. Once we have processed your payment, the extra CI minutes are synced to your personal namespace. 1. To confirm the available CI minutes for your personal projects, click your avatar, then go to **Settings > Usage Quotas**. The **Additional minutes** displayed now includes the purchased additional CI minutes, plus any minutes rolled over from last month. @@ -287,19 +294,51 @@ To purchase additional minutes for your personal namespace: Be aware that: - If you have purchased extra CI minutes before the purchase of a paid plan, - we will calculate a pro-rated charge for your paid plan. That means you may - be charged for less than one year since your subscription was previously + we calculate a pro-rated charge for your paid plan. That means you may + be charged for less than one year because your subscription was previously created with the extra CI minutes. -- Once the extra CI minutes have been assigned to a Group, they can't be transferred +- After the extra CI minutes have been assigned to a Group, they can't be transferred to a different Group. - If you have used more minutes than your default quota, these minutes will be deducted from your Additional Minutes quota immediately after your purchase of additional minutes. -## Customers portal +## Storage subscription + +Projects have a free storage quota of 10 GB. To exceed this quota you must first [purchase one or +more storage subscription units](#purchase-more-storage). Each unit provides 10 GB of additional +storage per namespace. A storage subscription is renewed annually. For more details, see +[Usage Quotas](../../user/usage_quotas.md). + +When the amount of purchased storage reaches zero, all projects over the free storage quota are +locked. Projects can only be unlocked by purchasing more storage subscription units. + +### Purchase more storage + +To purchase more storage for either a personal or group namespace: + +1. Sign in to GitLab.com. +1. From either your personal homepage or the group's page, go to **Settings > Usage Quotas**. +1. For each locked project, total by how much its **Usage** exceeds the free quota and purchased + storage. You must purchase the storage increment that exceeds this total. +1. Click **Purchase more storage** and you are taken to the Customers Portal. +1. Click **Add new subscription**. +1. Scroll to **Purchase add-on subscriptions** and select **Buy storage subscription**. +1. In the **Subscription details** section select the name of the user or group from the dropdown. +1. Enter the desired quantity of storage packs. +1. In the **Billing information** section select the payment method from the dropdown. +1. Select the **Privacy Policy** and **Terms of Service** checkbox. +1. Select **Buy subscription**. +1. Sign out of the Customers Portal. +1. Switch back to the GitLab.com tab and refresh the page. + +The **Purchased storage available** total is incremented by the amount purchased. All locked +projects are unlocked and their excess usage is deducted from the additional storage. + +## Customers Portal -GitLab provides a [customer portal](../index.md#customers-portal) where you can -manage your subscriptions and your account details. +The GitLab [Customers Portal](../index.md#customers-portal) enables you to manage your subscriptions +and account details. ## Contact Support diff --git a/doc/subscriptions/index.md b/doc/subscriptions/index.md index df71c6bcf31..d80a2ebe179 100644 --- a/doc/subscriptions/index.md +++ b/doc/subscriptions/index.md @@ -1,7 +1,7 @@ --- stage: none group: unassigned -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments type: index, reference --- @@ -27,7 +27,7 @@ When choosing a subscription, there are two factors to consider: There are some differences in how a subscription applies, depending if you use GitLab.com or a self-managed instance: -- [GitLab.com](gitlab_com/index.md): GitLab's software-as-a-service offering. +- [GitLab.com](gitlab_com/index.md): The GitLab software-as-a-service offering. You don't need to install anything to use GitLab.com, you only need to [sign up](https://gitlab.com/users/sign_up) and start using GitLab straight away. - [GitLab self-managed](self_managed/index.md): Install, administer, and maintain @@ -37,7 +37,7 @@ On a self-managed instance, a GitLab subscription provides the same set of features for _all_ users. On GitLab.com, you can apply a subscription to either a group or a personal namespace. -NOTE: **Note:** +NOTE: Subscriptions cannot be transferred between GitLab.com and GitLab self-managed. A new subscription must be purchased and applied as needed. @@ -77,7 +77,7 @@ With the [Customers Portal](https://customers.gitlab.com/) you can: - [Change your payment method](#change-your-payment-method) - [Change the linked account](#change-the-linked-account) - [Change the associated namespace](#change-the-associated-namespace) -- [Change customers portal account password](#change-customer-portal-account-password) +- [Change customers portal account password](#change-customers-portal-account-password) ### Change your personal details @@ -152,9 +152,9 @@ With a linked GitLab.com account: 1. Select the desired group from the **This subscription is for** dropdown. 1. Click **Proceed to checkout**. -Subscription charges are calculated based on the total number of users in a group, including its subgroups and nested projects. If the total number of users exceeds the number of seats in your subscription, you will be charged for the additional users. +Subscription charges are calculated based on the total number of users in a group, including its subgroups and nested projects. If the total number of users exceeds the number of seats in your subscription, your account is charged for the additional users. -### Change customer portal account password +### Change Customers Portal account password To change the password for this customers portal account: @@ -173,7 +173,7 @@ Find more information how to apply and renew at ## GitLab for Open Source subscriptions -All [GitLab for Open Source](https://about.gitlab.com/solutions/open-source/program/) +All [GitLab for Open Source](https://about.gitlab.com/solutions/open-source/join/) requests, including subscription renewals, must be made by using the application process. If you have any questions, send an email to `opensource@gitlab.com` for assistance. diff --git a/doc/subscriptions/self_managed/index.md b/doc/subscriptions/self_managed/index.md index a63c2830909..a4affff92e4 100644 --- a/doc/subscriptions/self_managed/index.md +++ b/doc/subscriptions/self_managed/index.md @@ -1,7 +1,7 @@ --- stage: none group: unassigned -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments type: index, reference --- @@ -45,13 +45,6 @@ billable user, with the following exceptions: - Members with Guest permissions on an Ultimate subscription. - GitLab-created service accounts: `Ghost User` and bots (`Support Bot`, [`Project bot users`](../../user/project/settings/project_access_tokens.md#project-bot-users), and so on). -### Users statistics - -To view a breakdown of the users within your instance, including active, billable, -and blocked, go to **Admin Area > Overview > Dashboard** and select **Users statistics** -in the **Users** section. For more details, see -[Users statistics](../../user/admin_area/index.md#users-statistics). - ### Tips for managing users and subscription seats Managing the number of users against the number of subscription seats can be a challenge: @@ -69,6 +62,7 @@ GitLab has several features which can help you manage the number of users: option. **Available in GitLab 13.6 and later**. - [Disable new sign-ups](../../user/admin_area/settings/sign_up_restrictions.md), and instead manage new users manually. +- View a breakdown of users by role in the [Users statistics](../../user/admin_area/index.md#users-statistics) page. ## Obtain a subscription @@ -79,20 +73,32 @@ To subscribe to GitLab through a self-managed installation: 1. After purchase, a license file is sent to the email address associated to the Customers Portal account, which must be [uploaded to your GitLab instance](../../user/admin_area/license.md#uploading-your-license). -TIP: **Tip:** +NOTE: If you're purchasing a subscription for an existing **Core** self-managed instance, ensure you're purchasing enough seats to [cover your users](../../user/admin_area/index.md#administering-users). ## View your subscription -If you are an administrator, to view the status of your self-managed subscription, -log in to the your GitLab instance and go to the **License** page: +If you are an administrator, you can view the status of your subscription: 1. Go to **Admin Area**. 1. From the left-hand menu, select **License**. -Read more about the [license admin area](../../user/admin_area/license.md). +The **License** page includes the following details: + +- Licensee +- Plan +- When it was uploaded, started, and when it expires + +It also displays the following important statistics: + +| Field | Description | +|:-------------------|:------------| +| Users in License | The number of users you've paid for in the current license loaded on the system. This does not include the amount you've paid for `Users over license` during renewal. | +| Billable users | The daily count of billable users on your system. | +| Maximum users | The highest number of billable users on your system during the term of the loaded license. If this number exceeds your users in license count at any point, you incur users over license. | +| Users over license | The number of users that exceed the `Users in License` for the current license term. Charges for this number of users are incurred at the next renewal. | ## Renew your subscription @@ -109,16 +115,16 @@ log in and verify or update: - The invoice contact details on the **Account details** page. - The credit card on file on the **Payment Methods** page. -TIP: **Tip:** +NOTE: Contact our [support team](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293) if you need assistance accessing the Customers Portal or if you need to change the contact person who manages your subscription. It's important to regularly review your user accounts, because: -- A GitLab subscription is based on the number of users. You will pay more than - you should if you renew for too many users, while the renewal will fail if you - attempt to renew a subscription for too few users. +- A GitLab subscription is based on the number of users. You pay more than you should if you renew + for too many users, while the renewal fails if you attempt to renew a subscription for too few + users. - Stale user accounts can be a security risk. A regular review helps reduce this risk. #### Users over License @@ -129,6 +135,10 @@ count exceeds the number included in the subscription, known as the number of _users over license_, you must pay for the excess number of users either before renewal, or at the time of renewal. This is also known as the _true up_ process. +To view the number of _Users over License_ go to the **Admin Area**. + +### Add users to a subscription + Self-managed instances can add users to a subscription any time during the subscription period. The cost of additional users added during the subscription period is prorated from the date of purchase through the end of the subscription period. @@ -140,10 +150,10 @@ To add users to a subscription: 1. Select **Add more seats** on the relevant subscription card. 1. Enter the number of additional users. 1. Select **Proceed to checkout**. -1. Review the **Subscription Upgrade Detail**. The system lists the total price for all users on the system and a credit for what you've already paid. You will only be charged for the net change. +1. Review the **Subscription Upgrade Detail**. The system lists the total price for all users on the system and a credit for what you've already paid. You are only be charged for the net change. 1. Select **Confirm Upgrade**. -The following will be emailed to you: +The following items are emailed to you: - A payment receipt. You can also access this information in the Customers Portal under [**View invoices**](https://customers.gitlab.com/receipts). - A new license. [Upload this license](../../user/admin_area/license.md#uploading-your-license) to your instance to use it. @@ -158,29 +168,16 @@ We recommend following these steps during renewal: 1. Determine if you have a need for user growth in the upcoming subscription. 1. Log in to the [Customers Portal](https://customers.gitlab.com/customers/sign_in) and select the **Renew** button beneath your existing subscription. - TIP: **Tip:** + NOTE: If you need to change your [GitLab tier](https://about.gitlab.com/pricing/), contact our sales team via `renewals@gitlab.com` for assistance as this can't be done in the Customers Portal. -1. In the first box, enter the total number of user licenses you’ll need for the upcoming year. Be sure this number is at least **equal to, or greater than** the number of active users in the system at the time of performing the renewal. +1. In the first box, enter the total number of user licenses you’ll need for the upcoming year. Be sure this number is at least **equal to, or greater than** the number of billable users in the system at the time of performing the renewal. 1. Enter the number of [users over license](#users-over-license) in the second box for the user overage incurred in your previous subscription term. - - TIP: **Tip:** - You can find the _users over license_ in your instance's **Admin** dashboard by clicking on the **Admin Area** in the top bar, or going to `/admin`. - - The following table describes details of your admin dashboard and renewal terms: - - | Field | Description | - |:------|:------------| - | Users in License | The number of users you've paid for in the current license loaded on the system. This does not include the amount you've paid for `Users over license` during renewal. | - | Active users | The daily count of active users on your system. | - | Maximum users | The highest number of active users on your system during the term of the loaded license. If this number exceeds your users in license count at any point, you incur users over license. | - | Users over license | The number of users that exceed the `Users in License` for the current license term. Charges for this number of users will be incurred at the next renewal. | - 1. Review your renewal details and complete the payment process. -1. A license for the renewal term will be available for download on the [Manage Purchases](https://customers.gitlab.com/subscriptions) page on the relevant subscription card. Select **Copy license to clipboard** or **Download license** to get a copy. +1. A license for the renewal term is available for download on the [Manage Purchases](https://customers.gitlab.com/subscriptions) page on the relevant subscription card. Select **Copy license to clipboard** or **Download license** to get a copy. 1. [Upload](../../user/admin_area/license.md#uploading-your-license) your new license to your instance. -An invoice will be generated for the renewal and available for viewing or download on the [View invoices](https://customers.gitlab.com/receipts) page. If you have difficulty during the renewal process, contact our [support team](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293) for assistance. +An invoice is generated for the renewal and available for viewing or download on the [View invoices](https://customers.gitlab.com/receipts) page. If you have difficulty during the renewal process, contact our [support team](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293) for assistance. ### Seat Link @@ -195,9 +192,9 @@ Seat Link provides **only** the following information to GitLab: - Date - License key - Historical maximum user count -- Active users count +- Billable users count -For offline or closed network customers, the existing [true-up model](#users-over-license) will be used. Prorated charges are not possible without user count data. +For offline or closed network customers, the existing [true-up model](#users-over-license) is used. Prorated charges are not possible without user count data. <details> <summary>Click here to view example content of a Seat Link POST request.</summary> @@ -306,18 +303,18 @@ When your subscription or trial expires, GitLab does not delete your data, but i may become inaccessible, depending on the tier at expiry. Some features may not behave as expected if you're not prepared for the expiry. For example, [environment specific variables not being passed](https://gitlab.com/gitlab-org/gitlab/-/issues/24759). -If you renew or upgrade, your data will again be accessible. +If you renew or upgrade, your data is again accessible. For self-managed customers, there is a 14-day grace period when your features -will continue to work as-is, after which the entire instance will become read +continue to work as-is, after which the entire instance becomes read only. -However, if you remove the license, you will immediately revert to Core -features, and the instance will be read / write again. +However, if you remove the license, you immediately revert to Core +features, and the instance become read / write again. -## Customers portal +## Customers Portal -GitLab provides a [customer portal](../index.md#customers-portal) where you can +GitLab provides the [Customers Portal](../index.md#customers-portal) where you can manage your subscriptions and your account details. ## Contact Support |