License

Verify the license scope, expiry, bound domain, and IP address in one place to see usage limits and expiration risk before they interrupt access.

Reaching the Screen

Panel menu: Help then License Information: {admin}/help/license

The entry is listed only for staff who hold the license privilege. The rest of the Help menu stays available to everyone who has one of its other privileges, but this page refuses even when its address is opened directly.

What Is on the Screen

Two cards. The first is the license itself, read top to bottom in three bands; the second lists whatever add-ons are attached to it.

The status strip

The headline reads License Active, with the product and plan beside it. It has an opposite state, but you will not meet it on this page: the moment a license stops verifying, the panel replaces every admin screen with the license error screen instead of rendering this one.

Time Remaining counts the days to the expiry date and switches to the warning style below 30 days; a license with no end date reads Unlimited. Term writes the same thing out as activation date, arrow, expiry date, and appends the billing cycle when the license carries one.

Two buttons sit at the right: Change License Key, which opens the key field in the band below, and Force License Update. Under them, Last Checked gives the moment the stored license data was fetched. That line is absent until a check has succeeded at least once.

The key band

The key is shown masked, with the prefix and the last four characters left readable. Two small buttons sit next to it and are drawn only when a key is actually recorded: an eye that swaps the mask for the whole key, and a clipboard that copies it.

Opposite the key, a padlock names the domain the license is bound to and a network icon its bound IP address. When the license does not name a domain, this installation's own domain is shown in its place; when it carries no IP lock, that cell shows a dash.

Installation facts

Five of the eight cells come with the answer from the license network: the holder, the two dates, the client limit and the copyright notice. The other three describe this installation itself: the version it is running, which is read from a file on disk, the PHP version of the process serving the panel, and the directory it sits in. Nothing here is edited from the panel. A holder or an activation date the license does not name is shown as a dash; the expiration date and the client limit read Unlimited instead, and an installed directory that is not known prints a single slash.

Add-ons

Everything attached to the license gets its own card: the add-on name, its state, the days it has left, a bar showing how much of its term has been spent, and the term dates underneath. The number of cards sits next to the Addons heading, and a summary line reads how many are active and how many are out of scope.

The order is not alphabetical. Anything still live comes first, and inside each group the soonest expiry leads, so whatever needs renewing is read first. The heading says so itself with Soonest expiration first.

An add-on running normally carries no mark at all: a mark appears only when the state deviates, as Expired, Cancelled or Suspended. Expired, cancelled and suspended cards are faded and drop the remaining-days figure, because there is none to show.

With nothing attached, the card holds an empty state and a button to the store instead of a list. With add-ons present, that same button returns as a band under the list, so the way to buy more is in the same place either way. Both open the store in a new tab.

Fields

Tasks

Re-check the license now

1. Press Force License Update in the status strip.
2. Wait for the button to read Update Completed; the page reloads itself a moment later. The label only says the request finished, not that the check succeeded.
3. If it succeeded, the strip, the facts and the add-on cards now come from a fresh answer and Last Checked shows the time you pressed the button. If it did not, the reload lands on the license error screen instead (see the warning below).

On this page, this is how you see a change made on the license side, such as a renewal or a newly attached add-on, before the stored answer expires on its own. A few premium module screens carry their own refresh button that does the same thing.

Replace the license key

1. Press Change License Key. The field opens under the key and takes the focus.
2. Type or paste the new key. Case and separators do not matter and the prefix is added for you, so a full key and a bare sixteen-character body are both accepted; the field rewrites itself into the grouped form when you leave it or paste into it.
3. Press Save & Verify. The button stays closed until the key is complete and different from the current one.
4. The key is verified before it is kept: on success the page reloads on the new license, and if the network refuses it, the refusal is shown and the old key stays in place.
5. If the key is a free developer license and the installation is not on a developer license today, the switch is not made straight away: your current license stays active and the Switch to a developer license? window opens. It explains that this license is not for commercial use and that a permanent development license notice will show in the admin area after the switch. Switch to Developer License completes it; closing the window changes nothing.

You can go back to a key this installation has verified before. The installation keeps the identity the license network issued for each of its last four keys. It sends that identity again on the way back, so the license does not need a reissue. A developer key you backed out of in the window stays bound to this installation on the license network. You can still confirm it here later; using it on another installation needs a reissue. If your license key was changed in your client account, saving the new key here is enough: the installation connects with the identity it has been using, so the license does not need a reissue.

Leave the license error screen

1. On the error screen, click Force License Update. If the license verifies, the panel opens.
2. When the installation has no stored key, the key field opens ready. Type the key and click Save & Verify.
3. When a key is stored, open the field with Change License Key. On this screen the button is enabled for the same key too.
4. Verification starts again. If the key is accepted, the page reloads on the license.

Move the installation to a new address

The license stays bound to the address it was verified on. After you move the installation to another domain or server, bind it to the new address:

1. In your WISECP client account, open the license and reissue it with the Reissue button. This releases the old address.
2. On the new server, rename the stored license file coremio/storage/LICENSE, for example to LICENSE.old. The panel stops sending you to the old address.
3. Open the admin panel at the new address and sign in. The license is verified again and bound to this address.
4. When this page shows the new domain, delete the renamed file.

Read or copy the whole key

1. Press the eye button next to the masked key to swap it for the full one.
2. Press the clipboard button to copy the key; a short confirmation appears on the button.
3. Press the eye again to put the mask back. Nothing else on the page changes, and the key is never revealed by loading the screen alone.

Things to Watch

Required Privileges

The Help section opens for staff holding any one of its privileges (HELP_HEALTH, HELP_UPDATES_LOOK, HELP_UPDATES_OPERATION, HELP_LICENSE, HELP_USE_GUIDE), but this page itself needs HELP_LICENSE and refuses without it. Both actions on the screen, forcing a re-check and replacing the key, run under that same privilege: seeing the license and changing its key are not separate rights here.

Related Articles

• Updates
• System Health
• Logo and Branding
• Privilege Groups
• Automation on Hold After a Move or a Copy