If the authorization is used and if the authorization fails, then the development environment isn't opened.
|Password||Password protecting the entrance into editing the application.|
|Confirm password||Check repeat of the entered password.|
|Licence keys list||Bind editing the application to the concrete number(s) of the licence keys and/or to the Unique user number (PmUserNumber). |
- either the licence key number prefaced by the 'k' prefix (e.g. k1028)
- or the Unique user number (PmUserNumber) prefaced by the 'g' prefix (e.g. g200).
- in case of key loss a new key can be bought, but it will have a different number and will not be suitable for application editing.
- one company may have multiple keys, requesting all of them to be usable for application editing.
Therefore it is better to protect the application by PmUserNumber, because this number is unique only for specific company and the same number can be burned into multiple development (or runtime) keys of this company.