Repository navigation
Update license key docs to match the Product license page - #2073
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Contributor
|
Direct preview links to pages changed in this PR: |
enriquegh
force-pushed
the
enrique/update-license-key-docs
branch
from
October 6, 2026 22:52
938a4c7 to
c8a2069
Compare
enriquegh
force-pushed
the
enrique/update-license-key-docs
branch
from
October 8, 2026 02:59
c8a2069 to
382a5f0
Compare
bobheadxi
reviewed
Oct 8, 2026
Comment on lines
+28
to
+31
| 1. Go to **Administration → Configuration → Product license** (`/admin/license`). | ||
| 2. Under **Update license key**, paste the new key into the **License key** field. | ||
| 3. Click **Validate & apply license key**. Sourcegraph checks the key and rejects one that is invalid or expired. | ||
| 4. In the **Confirm license update** dialog, compare the current license with the new one (customer, plan, seat count, and expiry date), then click **Confirm & apply license**. |
Member
There was a problem hiding this comment.
I feel like out of these 4 steps, only the first one is really needed right? Once you get to the page the rest should be self-explanatory
Contributor
Author
There was a problem hiding this comment.
What about:
1. Go to **Administration → Configuration → Product license** (`/admin/license`).
2. Under **Update license key**, paste the new key into the **License key** field. You will be taken through a series of steps to validate and confirm the new license before applying to the instance
Contributor
Author
There was a problem hiding this comment.
Mainly that I want it to be clear there are some steps after you input the license key and that these should be checked. Open to suggestions though
Member
There was a problem hiding this comment.
My suggestion would be something like:
Go to Administration → Configuration → Product license (
/admin/license). Here, you can update your license key, view details of your current license, and more.
Member
There was a problem hiding this comment.
If you land on that page and can't figure out how to update the key we probably have a problem 😆
Contributor
Author
There was a problem hiding this comment.
Fair, shortened things here.
bobheadxi
reviewed
Oct 8, 2026
|
|
||
| Any current Administrator can update your license key by going to Administration -> [Advanced configuration](/admin/config/site-config) | ||
| <Callout type="note"> | ||
| On [Sourcegraph Cloud](/cloud/#how-do-we-update-our-license-key), Sourcegraph manages your license key and the **Product license** page doesn't show the **Update license key** form. To apply a new or renewed license, contact your Sourcegraph account team or [support@sourcegraph.com](mailto:support@sourcegraph.com). |
Member
There was a problem hiding this comment.
Suggested change
| On [Sourcegraph Cloud](/cloud/#how-do-we-update-our-license-key), Sourcegraph manages your license key and the **Product license** page doesn't show the **Update license key** form. To apply a new or renewed license, contact your Sourcegraph account team or [support@sourcegraph.com](mailto:support@sourcegraph.com). | |
| On [Sourcegraph Cloud](/cloud/#how-do-we-update-our-license-key), Sourcegraph manages your license key. To apply a new or renewed license, contact your Sourcegraph account team or [support@sourcegraph.com](mailto:support@sourcegraph.com). |
bobheadxi
reviewed
Oct 8, 2026
| Sourcegraph's Kubernetes deployment [requires an Enterprise license key](https://about.sourcegraph.com/pricing). | ||
|
|
||
| Once you have a license key, add it to your [advanced configuration](/admin/config/site-config). | ||
| Once you have a license key, add it on the **Product license** page. See [How can we update our license key?](/admin/licensing#how-can-we-update-our-license-key) |
Member
There was a problem hiding this comment.
Suggested change
| Once you have a license key, add it on the **Product license** page. See [How can we update our license key?](/admin/licensing#how-can-we-update-our-license-key) | |
| Once you have a license key, configure it in **Administration → Configuration → Product license** (`/admin/license`). See [How can we update our license key?](/admin/licensing#how-can-we-update-our-license-key) |
Replace the outdated Site configuration steps with the Product license page flow, correct what happens when a license expires, and explain that Sourcegraph manages license keys on Sourcegraph Cloud. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-2198952b-2156-4c41-95b8-3d5b5c963010
Amp-Thread-ID: https://ampcode.com/threads/T-2198952b-2156-4c41-95b8-3d5b5c963010 Co-authored-by: Amp <amp@ampcode.com>
enriquegh
enabled auto-merge (squash)
October 8, 2026 22:40
enriquegh
force-pushed
the
enrique/update-license-key-docs
branch
from
October 8, 2026 22:40
c18de6c to
b286a1f
Compare
This was referenced Oct 8, 2026
enriquegh
added a commit
that referenced
this pull request
Oct 8, 2026
Applies two review suggestions from @bobheadxi on #2073 that came in after it merged: - `admin/licensing`: shorten the Sourcegraph Cloud note to say Sourcegraph manages the license key, without describing the hidden form ([comment](#2073 (comment))). - `self-hosted/deploy/kubernetes/configure`: name the exact page, **Administration → Configuration → Product license** (`/admin/license`) ([comment](#2073 (comment))). Amp thread: https://ampcode.com/threads/T-2198952b-2156-4c41-95b8-3d5b5c963010 Co-authored-by: Amp <amp@ampcode.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Customer feedback: the license key docs were out of date. They said to edit
licenseKeyunder Site admin > Configuration > Site configuration, which no longer exists. On Sourcegraph Cloud, the Product license page has no way to update the key, so the customer ended up editing Advanced configuration by hand.Changes:
admin/licensing: replace the old steps with a pointer to the Product license page, and drop the "takes 10-15 minutes, restart the frontend" note: the change applies on save. Correct the FAQ on expired licenses: only users who are not site admins are blocked. Note that on Cloud, Sourcegraph manages the license key (the form is hidden on Cloud), and point Cloud customers to their account team or support@sourcegraph.com. Note that the form is disabled whenSITE_CONFIGorSITE_CONFIG_FILEis set.admin/subscriptions: link to the licensing FAQ instead of repeating the outdated steps.cloud: add an FAQ entry on license keys for Cloud.self-hosted/deploy/kubernetes/configure: point "Add license key" to the Product license page.Checks:
pnpm run check links --check-anchors --check-self-linksreports no new findings (266 before and after), and CSpell found no issues in the changed pages.Amp thread: https://ampcode.com/threads/T-2198952b-2156-4c41-95b8-3d5b5c963010