> For the complete documentation index, see [llms.txt](https://vendex.gitbook.io/ledgerise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendex.gitbook.io/ledgerise/09-licensing/03-activating-your-license.md).

# activating your license

License activation switches your Ledgerise deployment from sandbox to production mode. Do this once — after your setup is complete, your team is invited, and your sandbox testing is done.

***

## before you activate

Work through this checklist first. Activation is permanent for the current deployment — there is no path back to sandbox mode without a fresh install.

* [ ] All adapters are configured with **production credentials** (not test API keys).
* [ ] Mapping rules are in place for all product lines and billers your platform handles.
* [ ] Your suspense account code is set in Settings → System.
* [ ] Reconciliation report sources and at least one rule set are configured.
* [ ] At least one named Admin account (not `admin@ledgerise.dev`) can sign in.
* [ ] Finance Officers and Auditors have been invited and can access the dashboard.
* [ ] Sandbox data has been reset: **Settings → System → Reset sandbox data**.

→ Full pre-activation checklist: [sandbox to production](/ledgerise/02-deployment/05-sandbox-to-production.md)

***

## how your license key is delivered

Ledgerise delivers license keys through a secure one-time retrieval flow:

1. Ledgerise sends you an email with a **one-time retrieval link**. The link is valid for a limited time.
2. Your **client ID** is sent to you separately — by phone, WhatsApp, or direct message — never in the same email as the link.
3. Visit the retrieval link and enter your client ID.
4. Copy the **license key** displayed on the page.
5. The page expires after you copy the key. It cannot be accessed again.

Keep the license key somewhere safe before closing the retrieval page. If you lose it before entering it, contact Ledgerise -- the existing key will be revoked and a new one reissued.

> Treat the license key like a database password. Enter it only in Settings → System. Do not put it in code, config files, environment variable documentation, Slack messages, or emails.

***

## activation steps

1. Go to **Settings → System**.
2. Scroll to the **License** section.
3. Enter your **commercial license key**.
4. Click **Activate License**. Ledgerise verifies the key before production mode is enabled.

![License key input](https://1276940017-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLZlOeIAICCNV1xnIVnrb%2Fuploads%2Fgit-blob-dac4dd04ff98ad1447cd64266960cf85b0f5559b%2Flicense-key-input.png?alt=media)

***

## confirming activation

After clicking Activate License, verify two things:

**In the dashboard:**

* The **Sandbox** badge in the top navigation bar disappears.
* Settings → System → License shows **Production License** with your tier name and a valid license state.

**Via the healthcheck endpoint:**

```bash
curl https://your-ledgerise-domain/healthcheck
```

Look for:

```json
{
  "environment_mode": "production",
  "license": {
    "state": "active",
    "tier": "Pro"
  }
}
```

If `environment_mode` still reads `"sandbox"`, the license was not applied. Double-check that you entered the license key exactly as it appeared on the retrieval page — no leading or trailing spaces.

![Production license status](https://1276940017-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLZlOeIAICCNV1xnIVnrb%2Fuploads%2Fgit-blob-de2197ea523bcb9e208544a6b2843efa9718e50d%2Fsystem-production-license.png?alt=media)

***

## after activation

Your deployment is now live. Journal entries will be submitted to your accounting system on the next engine run.

* Start your real data imports or switch your payment webhooks from test to production endpoints.
* Monitor the first 48–72 hours closely. → See [what to monitor after go-live](/ledgerise/01-getting-started/04-quickstart.md#what-to-monitor-after-go-live)