Direct answer: GitLab subscriptions purchased through the Customers Portal auto-renew by default unless auto-renewal is turned off. GitLab treats Cancel subscription in the portal as disabling the next renewal, and an expired paid tier can fall back to Free-tier functionality rather than instantly deleting the namespace.
A GitLab cancellation should be treated as a transaction-specific workflow. Start with “Portal subscriptions auto-renew by default”: GitLab documents automatic renewal as the default for subscriptions purchased through the Customers Portal. Then record the rule behind “Cancel subscription disables auto-renew.” Keeping those two GitLab points visible makes it easier to separate the cancellation action from any refund, credit, fee, access, or equipment result.
GitLab policy checkpoints that control the outcome
Portal subscriptions auto-renew by default
For GitLab, review the billing trail tied to “Portal subscriptions auto-renew by default.” GitLab documents automatic renewal as the default for subscriptions purchased through the Customers Portal. That GitLab checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Cancel subscription disables auto-renew” as the next GitLab marker. In Subscription actions, Cancel subscription turns off automatic renewal and the card changes to show an expiration date. Compare the two GitLab markers before acting; the matching GitLab action here is “Open the GitLab Customers Portal and record the subscription card status.” Save the resulting GitLab confirmation so the later outcome can be checked against both rules.
Cancel subscription disables auto-renew
For GitLab, confirm the account history tied to “Cancel subscription disables auto-renew.” In Subscription actions, Cancel subscription turns off automatic renewal and the card changes to show an expiration date. That GitLab checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Seat counts can affect renewal cost” as the next GitLab marker. GitLab warns that billable users above the current subscription quantity can increase the renewed seat count automatically. Compare the two GitLab markers before acting; the matching GitLab action here is “Review billable users and seat quantity before touching auto-renewal.” Save the resulting GitLab confirmation so the later outcome can be checked against both rules.
Seat counts can affect renewal cost
For GitLab, map the booking file tied to “Seat counts can affect renewal cost.” GitLab warns that billable users above the current subscription quantity can increase the renewed seat count automatically. That GitLab checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Fewer-seat renewals need preparation” as the next GitLab marker. To renew for fewer seats, customers should reduce billable users and use the supported manual-renewal or sales route. Compare the two GitLab markers before acting; the matching GitLab action here is “Use Subscription actions > Cancel subscription to turn off the next automatic renewal.” Save the resulting GitLab confirmation so the later outcome can be checked against both rules.
Fewer-seat renewals need preparation
For GitLab, reconcile the confirmation set tied to “Fewer-seat renewals need preparation.” To renew for fewer seats, customers should reduce billable users and use the supported manual-renewal or sales route. That GitLab checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Failed renewal has a grace period” as the next GitLab marker. GitLab documents a 14-day period to renew after an auto-renewal failure before the paid tier is downgraded. Compare the two GitLab markers before acting; the matching GitLab action here is “Record the displayed expiration date and any renewal invoice information.” Save the resulting GitLab confirmation so the later outcome can be checked against both rules.
Failed renewal has a grace period
For GitLab, trace the purchase record tied to “Failed renewal has a grace period.” GitLab documents a 14-day period to renew after an auto-renewal failure before the paid tier is downgraded. That GitLab checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Free-tier operation can remain” as the next GitLab marker. After expiry, GitLab says customers can activate a new subscription or keep using Free-tier features after the paid license is removed where applicable. Compare the two GitLab markers before acting; the matching GitLab action here is “After expiry, verify whether the namespace is operating on Free-tier features or a replacement subscription.” Save the resulting GitLab confirmation so the later outcome can be checked against both rules.
Free-tier operation can remain
For GitLab, verify the service record tied to “Free-tier operation can remain.” After expiry, GitLab says customers can activate a new subscription or keep using Free-tier features after the paid license is removed where applicable. That GitLab checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Portal subscriptions auto-renew by default” as the next GitLab marker. GitLab documents automatic renewal as the default for subscriptions purchased through the Customers Portal. Compare the two GitLab markers before acting; the matching GitLab action here is “Open the GitLab Customers Portal and record the subscription card status.” Save the resulting GitLab confirmation so the later outcome can be checked against both rules.
GitLab policy map at a glance
| Decision point | Official GitLab rule |
|---|---|
| Portal subscriptions auto-renew by default | GitLab documents automatic renewal as the default for subscriptions purchased through the Customers Portal. |
| Cancel subscription disables auto-renew | In Subscription actions, Cancel subscription turns off automatic renewal and the card changes to show an expiration date. |
| Seat counts can affect renewal cost | GitLab warns that billable users above the current subscription quantity can increase the renewed seat count automatically. |
| Fewer-seat renewals need preparation | To renew for fewer seats, customers should reduce billable users and use the supported manual-renewal or sales route. |
Real GitLab situations that change the answer
Subscription card says Auto-renews on a future date
The example “Subscription card says Auto-renews on a future date” is useful for GitLab because Cancel subscription changes the renewal state rather than deleting the GitLab group immediately.
Verify it against “Seat counts can affect renewal cost” in this GitLab policy. GitLab warns that billable users above the current subscription quantity can increase the renewed seat count automatically. The pair defines the GitLab expectation more precisely than the word cancel alone.
Company wants fewer seats next year
For GitLab, “Company wants fewer seats next year” produces a specific money outcome: The team should reduce billable users and plan a supported lower-seat renewal instead of expecting seat count to fall automatically.
Check that GitLab result beside “Fewer-seat renewals need preparation.” To renew for fewer seats, customers should reduce billable users and use the supported manual-renewal or sales route. The two GitLab records should point to the same policy branch.
Auto-renew payment fails
The GitLab case “Auto-renew payment fails” should not be generalized. GitLab provides a 14-day renewal period before the paid tier is downgraded.
Its companion GitLab checkpoint is “Failed renewal has a grace period”: GitLab documents a 14-day period to renew after an auto-renewal failure before the paid tier is downgraded. Keep both GitLab details with the transaction record.
Paid term reaches its expiration date with no renewal
Use “Paid term reaches its expiration date with no renewal” as a GitLab case study. The expected timing outcome is: Free-tier functionality can remain available, subject to the offering and license state.
Now compare this GitLab case with “Free-tier operation can remain.” After expiry, GitLab says customers can activate a new subscription or keep using Free-tier features after the paid license is removed where applicable. That comparison explains which GitLab condition controls.
How to carry out a GitLab cancellation or refund request
GitLab action 1: Open the GitLab Customers Portal and record the subscription card status
Action 1 for GitLab is “Open the GitLab Customers Portal and record the subscription card status.” Its supporting GitLab rule is “Portal subscriptions auto-renew by default,” and the key record is the transaction identity.
The GitLab situation “Subscription card says Auto-renews on a future date” supplies the comparison point: Cancel subscription changes the renewal state rather than deleting the GitLab group immediately. Check the completed GitLab record against that result.
GitLab action 2: Review billable users and seat quantity before touching auto-renewal
At GitLab, action 2 is “Review billable users and seat quantity before touching auto-renewal.” The GitLab checkpoint “Cancel subscription disables auto-renew” makes the issuing channel worth recording.
Test that GitLab action against “Company wants fewer seats next year.” The team should reduce billable users and plan a supported lower-seat renewal instead of expecting seat count to fall automatically. Keep the final GitLab screen or email if the real result needs follow-up.
GitLab action 3: Use Subscription actions > Cancel subscription to turn off the next automatic renewal
For GitLab, perform “Use Subscription actions > Cancel subscription to turn off the next automatic renewal” only after matching the service status to “Seat counts can affect renewal cost.” That GitLab rule is: GitLab warns that billable users above the current subscription quantity can increase the renewed seat count automatically.
The case “Auto-renew payment fails” shows how GitLab can behave in practice: GitLab provides a 14-day renewal period before the paid tier is downgraded. Use this GitLab confirmation to verify the same branch applied.
GitLab action 4: Record the displayed expiration date and any renewal invoice information
The GitLab workflow now reaches “Record the displayed expiration date and any renewal invoice information.” Record the confirmation date before completing it, because “Fewer-seat renewals need preparation” controls this GitLab branch.
Afterward, compare the GitLab result with “Paid term reaches its expiration date with no renewal.” Free-tier functionality can remain available, subject to the offering and license state. A mismatch should be documented before another GitLab request is sent.
GitLab action 5: After expiry, verify whether the namespace is operating on Free-tier features or a replacement subscription
Use “After expiry, verify whether the namespace is operating on Free-tier features or a replacement subscription” as the next GitLab action. Pair it with the GitLab rule “Failed renewal has a grace period,” especially the deadline attached to that rule.
For the example “Subscription card says Auto-renews on a future date,” Cancel subscription changes the renewal state rather than deleting the GitLab group immediately. That GitLab example gives a concrete result to compare with the completed action.
Verify the final GitLab status
Start the GitLab closeout with “Free-tier operation can remain.” After expiry, GitLab says customers can activate a new subscription or keep using Free-tier features after the paid license is removed where applicable.
Then test “Portal subscriptions auto-renew by default” against the final GitLab screen. GitLab documents automatic renewal as the default for subscriptions purchased through the Customers Portal.
The GitLab example “Paid term reaches its expiration date with no renewal” should also fit: Free-tier functionality can remain available, subject to the offering and license state.
If those GitLab records disagree, note the exact date, product, biller, fare, plan, or property before support is contacted.
GitLab transaction worksheet
GitLab worksheet 1: Portal subscriptions auto-renew by default
Compare this GitLab checkpoint “Portal subscriptions auto-renew by default” with this GitLab case “Company wants fewer seats next year.” The official GitLab point is: GitLab documents automatic renewal as the default for subscriptions purchased through the Customers Portal.
For “Company wants fewer seats next year,” GitLab gives this practical result: The team should reduce billable users and plan a supported lower-seat renewal instead of expecting seat count to fall automatically. The related GitLab action is “Use Subscription actions > Cancel subscription to turn off the next automatic renewal.” Save this GitLab confirmation that shows which result occurred.
GitLab worksheet 2: Cancel subscription disables auto-renew
Verify this GitLab checkpoint “Cancel subscription disables auto-renew” with this GitLab case “Auto-renew payment fails.” The official GitLab point is: In Subscription actions, Cancel subscription turns off automatic renewal and the card changes to show an expiration date.
For “Auto-renew payment fails,” GitLab gives this practical result: GitLab provides a 14-day renewal period before the paid tier is downgraded. The related GitLab action is “Record the displayed expiration date and any renewal invoice information.” Save this GitLab confirmation that shows which result occurred.
GitLab worksheet 3: Seat counts can affect renewal cost
Map this GitLab checkpoint “Seat counts can affect renewal cost” with this GitLab case “Paid term reaches its expiration date with no renewal.” The official GitLab point is: GitLab warns that billable users above the current subscription quantity can increase the renewed seat count automatically.
For “Paid term reaches its expiration date with no renewal,” GitLab gives this practical result: Free-tier functionality can remain available, subject to the offering and license state. The related GitLab action is “After expiry, verify whether the namespace is operating on Free-tier features or a replacement subscription.” Save this GitLab confirmation that shows which result occurred.
GitLab worksheet 4: Fewer-seat renewals need preparation
Pair this GitLab checkpoint “Fewer-seat renewals need preparation” with this GitLab case “Subscription card says Auto-renews on a future date.” The official GitLab point is: To renew for fewer seats, customers should reduce billable users and use the supported manual-renewal or sales route.
For “Subscription card says Auto-renews on a future date,” GitLab gives this practical result: Cancel subscription changes the renewal state rather than deleting the GitLab group immediately. The related GitLab action is “Open the GitLab Customers Portal and record the subscription card status.” Save this GitLab confirmation that shows which result occurred.
What to save for this GitLab transaction
- GitLab original receipt, ticket, invoice, booking, or membership record
- GitLab policy checkpoint “Portal subscriptions auto-renew by default” with the date that makes it relevant
- GitLab billing or issuing channel tied to the transaction
- GitLab cancellation, downgrade, return, or booking-change confirmation
- GitLab effective end date or next controlling date
- GitLab refund, credit, fee, or equipment-return reference when the policy creates one
GitLab cancellation and refund FAQ
How does “Portal subscriptions auto-renew by default” affect a GitLab cancellation?
GitLab publishes this rule: GitLab documents automatic renewal as the default for subscriptions purchased through the Customers Portal. In GitLab practice, “Subscription card says Auto-renews on a future date” adds this result: Cancel subscription changes the renewal state rather than deleting the GitLab group immediately.
How does “Cancel subscription disables auto-renew” affect a GitLab cancellation?
GitLab publishes this rule: In Subscription actions, Cancel subscription turns off automatic renewal and the card changes to show an expiration date. The GitLab case “Company wants fewer seats next year” gives the practical check: The team should reduce billable users and plan a supported lower-seat renewal instead of expecting seat count to fall automatically.
How does “Seat counts can affect renewal cost” affect a GitLab cancellation?
GitLab publishes this rule: GitLab warns that billable users above the current subscription quantity can increase the renewed seat count automatically. Compare that GitLab rule with “Auto-renew payment fails,” where GitLab provides a 14-day renewal period before the paid tier is downgraded.
How does “Fewer-seat renewals need preparation” affect a GitLab cancellation?
GitLab publishes this rule: To renew for fewer seats, customers should reduce billable users and use the supported manual-renewal or sales route. For a concrete GitLab example, “Paid term reaches its expiration date with no renewal” means: Free-tier functionality can remain available, subject to the offering and license state.
How does “Failed renewal has a grace period” affect a GitLab cancellation?
GitLab publishes this rule: GitLab documents a 14-day period to renew after an auto-renewal failure before the paid tier is downgraded. The GitLab scenario “Subscription card says Auto-renews on a future date” narrows the answer: Cancel subscription changes the renewal state rather than deleting the GitLab group immediately.
How does “Free-tier operation can remain” affect a GitLab cancellation?
GitLab publishes this rule: After expiry, GitLab says customers can activate a new subscription or keep using Free-tier features after the paid license is removed where applicable. Use the GitLab situation “Company wants fewer seats next year” as the cross-check: The team should reduce billable users and plan a supported lower-seat renewal instead of expecting seat count to fall automatically.
Which GitLab records are worth keeping after the request?
Keep the original GitLab transaction record, the effective change date, and the final GitLab confirmation. Store any approved GitLab refund, credit, fee, or return reference with the payment or booking record.
What changes when a third party controls this GitLab transaction?
Use this GitLab source that assigns responsibility to the app store, travel agent, property, club, or other biller. The correct GitLab route is the one that reaches the party that actually issued the charge, booking, or ticket.
Related RefundGuides pages for GitLab readers
For GitLab, these existing RefundGuides pages provide nearby software apps navigation. They are supporting context only; the linked official GitLab policy controls the transaction described here.
- Grammarly Cancellation & Refund Guide: Auto-Renewal, Paid Access and Billing Errors
- Canva Subscription Cancellation & Refund Guide: Renewals, Trials, Teams and Paid Periods
- Miro Cancellation & Refund Guide: Paid-Period Access, Unused Time and Outstanding Licenses
Official GitLab sources checked on 2026-09-15
Official GitLab documentation below was checked on 2026-09-15. Recheck the applicable GitLab source before a later purchase or cancellation because the controlling terms can change.