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

# Shared Licenses

Shared licenses let you give a collaborator access to a Hedge app without ever handing over your own license key. Instead of copying your key into an email or DM, you share an activation directly from your license — Hedge generates a temporary, dedicated key for that person, and you stay in control of it.

{% hint style="info" %}
Shared licenses are available for Pro accounts with more than one activation.
{% endhint %}

### Who it's for

Shared licenses are for producers and post supervisors who work with (external) collaborators across projects. Manage app access without the administrative overhead or security risks of passing keys around.

### How it works

When you share an activation, you don't share your license key; Hedge creates a separate, temporary activation key on your behalf and sends it to your collaborator. Your original key remains private, and the shared key draws from your existing pool of activations. Revoke it at any time.

### Sharing a license

1. Sign in to the [License Manager](https://account.hedge.video/) and open the license you want to share.
2. Choose Share activation.
3. Enter your collaborator's email address.
4. Confirm. They receive their own temporary activation key by email, no need to copy it yourself.

<figure><img src="/files/H90eSkhHPFTRoVECBGBf" alt=""><figcaption></figcaption></figure>

Your collaborator activates the app with the key they're sent, just like any other activation (see [Activating](https://docs.hedge.video/general/licenses/activating)). No need to log in or create an account.

{% hint style="info" %}
A shared activation counts against the activations on your license, just like activating on one of your own computers. To protect your own license key, you can share all but one of your activations.
{% endhint %}

### Revoking access

Projects end, contracts wrap, and teams change. You can revoke a shared license at any time, without affecting your own activation or anyone else's.

1. Go to your license in the [License Manager](https://account.hedge.video/).
2. Find the shared activation by the collaborator's email address.
3. Choose Revoke. The shared key immediately stops working, and the activation returns to your pool.

<figure><img src="/files/dzv582TGgxwDrGYZMUx8" alt=""><figcaption></figcaption></figure>

There's no need to ask the other person to deactivate anything on their end. To make sure you don't get called, we email them explaining that their shared license has been revoked by its owner.

### Requirements

Sharing a license key is available for Pro licenses with more than one activation, as the first activation is always reserved for yourself.

The license also needs to be eligible for updates and support at the time you share your activation(s), to ensure your collaborator starts on the latest release for the best possible experience. If you later choose not to renew, the shared key continues to work on the last version your license does support — it simply won't receive newer releases, until you extend your license.


---

# 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://docs.hedge.video/general/licenses/shared-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.