> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/using-my-account/my-account/purchased-player-upgrades.md).

# Purchased Player Upgrades

Once purchased you need to Upgrade your Players so that they will automatically migrate between Licence Pool versions and consume upgrade licences as necessary

Licences are available for purchase at the ‘latest version’ and are automatically downgraded 1 previous major version if required. This results in an upgrade licence being issued which can be used for upgrading in the future.

{% hint style="info" %}
 **Example Scenario:** A customer has a v3 CMS and some v3 Players and needs an additional licence. The customer purchases an additional licence, which currently means a v4 licence is issued. On using this licence to connect another v3 Player to the existing licence pool, it will automatically downgrade the purchased v4 licence to a v3 licence so that their player can be licensed. This situation will also issue a v3 to v4 upgrade so that the customer can upgrade in the future and use the licence on a v4 player with no additional charges.
{% endhint %}

{% hint style="warning" %}
If you need to downgrade to earlier version, please open a [Ticket](https://account.xibosignage.com/my-account/tickets?open=true) with our help desk
{% endhint %}

It is technically possible to run a mismatched series of CMS and Player, providing that the CMS is of a higher or equal version than the Player. So for example, a v3 Player can run in compatibility mode against a v4 CMS, using a v3 Player licence.

{% hint style="success" %}
For the best results, we would always recommend running a **Player** and **CMS** from the **same major version**.
{% endhint %}

### **If you have upgrades but no available licences:**

* **Existing connected players**: upgrade your existing players.
* **New players**: un-licence one of your existing players, and install the new version onto the new player.

If you have a number of upgrades greater than the number of connected players, install the new version onto your new player, the licence upgrade will happen automatically.

### **If you have available licences:**

Firstly, ensure you know what version you want to use and what version you currently have.

* If you want to use the new major version, you can purchase an upgrade then install the new version onto your player.
* If you want to use the earlier version you can install the older version onto your player and it will find your available licence.
* If you have an available licence for the new major version, you should install the new version onto your player and it will find your available licence.

{% hint style="warning" %}
The version of your licence must match the version of the installation file that you want to install onto your player.
{% endhint %}


---

# 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.xibosignage.com/using-my-account/my-account/purchased-player-upgrades.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.