> For the complete documentation index, see [llms.txt](https://merithic.gitbook.io/merithic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://merithic.gitbook.io/merithic-docs/selling/licenses.md).

# Licenses and keys

A **license** is one buyer's right to use one product. It carries a **key** unique to them, which your product checks at runtime.

## Where to find them

**Products → your product → Licenses** lists everyone who owns it.

You can view owners by their **Roblox** identity or their **Discord** identity using the toggle above the table. Licenses always belong to the Roblox account; the Discord view is only a different way of displaying the same person, useful if you know your buyers by their Discord handle.

Buyers who haven't linked a Discord account show as *not linked* and fall back to their Roblox name.

## What you can do

| Action         | Effect                                                                                                      |
| -------------- | ----------------------------------------------------------------------------------------------------------- |
| **Transfer**   | Move the license to another Roblox user. The original owner loses access.                                   |
| **Rotate key** | Issue a new key. The old one stops working immediately. Use this when a key leaks.                          |
| **Pause**      | Suspend access without deleting. Their key is removed until you unpause.                                    |
| **Revoke**     | Delete the license permanently.                                                                             |
| **Blacklist**  | Block the user from every product in your studio. See [Blocking users](/merithic-docs/selling/blocking.md). |

{% hint style="info" %}
**Pause** and **rotate key** are reversible; **revoke** isn't. If you're responding to a suspected leak, rotate first, because it invalidates the leaked copy without punishing a legitimate buyer.
{% endhint %}

## Granting a license manually

**Add license** on the Licenses page grants access to any Roblox user without a purchase. They receive a key exactly like a normal buyer.

Manually granted licenses are excluded from revenue and sales figures, so your numbers stay honest.

## Leaked keys

When a key is used under a different Roblox user ID than the one it was issued to, the request fails and a **leaked key** alert appears under **Alerts**.

That tells you which product and which buyer's key is circulating. Rotate that key to kill the leaked copy.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://merithic.gitbook.io/merithic-docs/selling/licenses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.