Your client area, and what is on the service page

The dashboard is built around one question: what do I own, and is it working? Everything else is one click from there.

1. What you see when you log in

Panel	What it tells you
Services	Every product you own, its status, and its licence key
Invoices	What is unpaid, and a direct route to pay it
Tickets	Open conversations and whether the ball is with you or with us
Store	The catalogue, with what you already own marked

2. The service page is the important one

Open any service and you get the things a licensed module actually needs:

Licence key — the one to paste into the module's settings.
Licensed domain and installation path — where that key is currently bound. Before first use both read not activated yet; they fill in by themselves the first time your module checks in.
Download — the current build, with its checksum.
Move Installation — releases the licence so it can bind somewhere else.

"Not activated yet" is normal on a key you have just bought. A licence binds to the first installation that validates it. Until you install the module and it checks in, there is nothing to show — and that is also why the key is useless to anyone who has not installed it yet.

3. Downloads always give you the current build

The download on a service is not the file you bought; it is whatever we publish today for that product. Updates are included for as long as the licence is active, so the way to update is simply to download again.

Every build has a checksum shown next to it. If you care to check, the file you receive should match it exactly.

4. Moving to another server

Open the service and press Move Installation. It tells you what the licence is bound to and how many moves you have left before it confirms.

Install the module on the new server and enter the same key.

The licence binds there at its first check, and the old installation stops working at its next one.

Releasing is not reversible and it uses one of your moves. The module stops working on the current installation, so do it when you are ready to install on the new one, not in advance.