Apply a licence

A new Profinity installation runs without a licence file. An unlicensed Desktop installation is limited to personal, non-commercial use, and other installations start a one-time 14-day local trial with the Server features, as described in Licensing. A commercial or evaluation licence from Prohelion removes those limits, and you apply it after installation in the same way on every platform.

You need three things:

The Security administration permission, which is needed to view or change the License page. On a Windows desktop installation the built-in account holds it.
The licence file, named license.yaml, which Prohelion signs for one installation and returns after receiving its fingerprint.
Access to the machine that runs Profinity, or to its artefacts directory, when the instance has no network access.

Apply a licence from the License page

Select ADMIN in the side menu, then License.
Copy the Fingerprint with the copy button beside it, and send it to Prohelion through the usual sales or support channel. The fingerprint identifies this installation and is the only information Prohelion needs to issue a licence.
When Prohelion returns the license.yaml file, return to the License page, select Update license file, and choose the file.
Restart Profinity if the licence adds features, in particular a Server licence, because the address the web interface listens on is set when Profinity starts.

Profinity checks the file's signature, its expiry, and that its fingerprint matches this installation before it applies the file. If any check fails, the upload is rejected and the existing licence, if there is one, stays in effect. The fingerprint and the returned file can travel by any route, such as email from another computer, a USB drive, or a secure file copy, so the machine that runs Profinity does not need internet access.

Apply a licence without the web interface

For Docker, Linux services, and scripted deployments, copy the file into the artefacts directory instead.

Copy license.yaml into the license folder of the artefacts directory, so that the file ends up at license/license.yaml.
On Docker, place it in the mounted volume that holds the artefacts directory, so that it survives the container being recreated.
Restart Profinity if the licence adds features, or if the License page still shows the previous state.

The licence must belong to the installation's own fingerprint, in the same way as one uploaded from the page. To read the fingerprint without the web interface, open the License page from a browser on the same machine, or refer to the machine fingerprint.

Check that the licence has taken effect

Open ADMIN, then License, and check these three things:

State reads Valid, or Expiring when 30 days or fewer remain before the licence expires.
Expires, Customer, and Edition match the licence that Prohelion issued.
The Licensed features and Licensed component groups tables show the expected entries as licensed and available.

If the page still shows the previous state after you copied the file into the folder, restart Profinity and check again. Removing licensed features restarts Profinity automatically.

If the licence is rejected

What the page or message shows	Likely cause	What to do
The upload is rejected	The file's signature, expiry, or fingerprint did not pass validation. A file issued for a different machine is rejected with the message "License is not valid for this instance." and is not saved	Check that the file is the unchanged `license.yaml` that Prohelion returned, and that it has not expired
`WrongInstance` as the State after a `license.yaml` is copied into the `license` folder	The file was issued for a different machine	Send Prohelion the fingerprint shown on this installation, and apply the file that is issued for it
`Expired`	The licence's expiry date has passed	Ask Prohelion for a renewal, and apply it in the same way

A rejected upload never replaces a working licence, so it is safe to retry. For editions, features, and the 14-day local trial, refer to Licensing.