Commit ba3199f0 authored by Suzanne Selhorn's avatar Suzanne Selhorn Committed by Amy Qualls

Standardized expiration language

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/325346
parent b5dc272b
...@@ -237,12 +237,11 @@ To remove a billable user: ...@@ -237,12 +237,11 @@ To remove a billable user:
## Subscription expiry ## Subscription expiry
When your subscription or trial expires, GitLab does not delete your data, but When your subscription expires, you can continue to use GitLab for 14 days.
it may become inaccessible, depending on the tier at expiry. Some features may not On the 15th day, paid features are no longer available. You can
behave as expected if you're not prepared for the expiry. For example, continue to use free features.
[environment specific variables not being passed](https://gitlab.com/gitlab-org/gitlab/-/issues/24759).
If you renew or upgrade, your data is accessible again. To resume paid feature functionality, purchase a new subscription.
## CI pipeline minutes ## CI pipeline minutes
......
...@@ -318,18 +318,15 @@ The new tier takes effect when the new license is uploaded. ...@@ -318,18 +318,15 @@ The new tier takes effect when the new license is uploaded.
## Subscription expiry ## Subscription expiry
When your subscription or trial expires, GitLab does not delete your data, but it When your license expires, GitLab locks down features, like Git pushes
may become inaccessible, depending on the tier at expiry. Some features may not and issue creation. Then, your instance becomes read-only and
behave as expected if you're not prepared for the expiry. For example, an expiration message is displayed to all administrators.
[environment specific variables not being passed](https://gitlab.com/gitlab-org/gitlab/-/issues/24759).
If you renew or upgrade, your data is again accessible. For GitLab self-managed instances, you have a 14-day grace period
before this occurs.
For GitLab self-managed customers, there is a 14-day grace period when your features
continue to work as-is, after which the entire instance becomes read - To resume functionality, upload a new license.
only. - To fall back to Free features, delete the expired license.
However, if you remove the license, you immediately revert to Free
features, and the instance become read / write again.
## Contact Support ## Contact Support
......
...@@ -99,12 +99,15 @@ license, otherwise you miss all the paid features if your license expires. ...@@ -99,12 +99,15 @@ license, otherwise you miss all the paid features if your license expires.
## What happens when your license expires ## What happens when your license expires
In case your license expires, GitLab locks down some features like Git pushes, When your license expires, GitLab locks down features, like Git pushes
and issue creation, and displays a message to all administrators to inform of the expired license. and issue creation. Then, your instance becomes read-only and
an expiration message is displayed to all administrators.
To get back all the previous functionality, you must upload a new license. For GitLab self-managed instances, you have a 14-day grace period
To fall back to having only the Free features active, you must delete the before this occurs.
expired license(s).
- To resume functionality, upload a new license.
- To fall back to Free features, delete the expired license.
### Remove a license ### Remove a license
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment