> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/administration/additional-troubleshooting/how-to-install-and-renew-your-s-docs-license-key-legacy.md).

# How to Install & Renew Your S-Docs License Key (Legacy)

> ⚠️ Important Update: S-Docs no longer uses license keys for subscriptions purchased after the Fall '24 (8.0) release. You only need to follow these steps if your organization is using an older, legacy version of S-Docs.

#### Steps to Renew or Update Your Key

If you are renewing your account or upgrading from a trial on a legacy version, follow these quick steps:

1. Open S-Docs: Click the App Launcher in the upper left corner, search for "S-Docs," and select the app.
2. Navigate to Templates: Click the dropdown arrow on the object tab and select S-Docs Templates.
3. Find the License Key Template: Locate your license key template. *(Tip: If you don't see it, filter the list view to "All Inactive Templates" and search for "License Key").*
4. Edit the Record: Click the template's name to open the record, then click Edit.
5. Apply the New Key: Find the Document Version field, delete the current text, and paste in your new license key.
6. Save & Verify: Click Save. The Document Version field should immediately update to display `***KEY ACCEPTED***`.

Your license key is now updated!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sdocs.com/sdocs/administration/additional-troubleshooting/how-to-install-and-renew-your-s-docs-license-key-legacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.