What is named user license

Get a Datasheet Grab a Meeting. Even More Information. Success Stories. Get Pricing Zentitle Overview for Hardware Licensing Easily reduce SKU hardware differentiation and increase revenue by creating instant upsell opportunities for your customers with Zentitle. Partners Blog Glossary Get the Newsletter.

Software Licensing. When licensing their software, many manufacturers distinguish between named pay-per-license and concurrent pay-per-use licenses. Both models differ in essential points. But what are the differences? What is the best model for your specific requirements?

Here are answer to all important questions and clarify which licensing model is recommended in which situation. Named licenses give an exact number of registered users the right to use a resource, e. This means that only a predefined number of selected users may access the resource. Named licenses are also known as single licenses or user licenses. Accordingly, the number of licenses is in a 1-to-1 ratio to the number of users.

For example, a software that is licensed in a company with three named users can also be used by three registered users only.

In the classic sense, concurrent licenses, also known as group licenses, give you the right to use a resource for a group of users. A volume licensing program also may be a named user license, where the name on the license is the name of an organization, permitting anyone the organization authorizes to use the product. This is appropriate for wide usage of a product throughout an organization and usually applies to licensing from a minimum of five, up to an unlimited maximum number of users.

The idea is to offer a highly discounted license for multiple users as would be common with a product that everyone needs, for example word processing software. By: Justin Stoltzfus Contributor, Reviewer. By: Satish Balakrishnan. Dictionary Dictionary Term of the Day. Machine Intelligence. Techopedia Terms. Connect with us. Since the system is operated by the developer, he can effectively control how the licenses are being used. Similar to when the license is bound to a specific user name, CodeMeter can again set the maximum number of accounts in the license and monitor them in the software.

The special advantage of CodeMeter in this case is that it can combine Software as a Service with on-premise software or act as a token for the reliable identification of a user. Excellent controls are possible by binding the license to the log-in name of the user. This option has been completely remodeled for CodeMeter 6.

In this case, the developer chooses whether the license is tied to a user name, a user name and domain, or a user name chosen by the developer himself. When licenses are bound to a user name with or without specified domain, CodeMeter handles almost the entire process automatically. The developer simply needs to add the right user names and, optionally, domain. When the license is used, CodeMeter Runtime checks the user name and domain automatically on the client PC. If a fitting Named User license is available, it would be used first.

Otherwise, a Concurrent User license is chosen. If neither a Named User nor Concurrent User license, an error message is displayed. A user name from an existing database can be used for binding the license to a user name.

But what happens to the process when user names change? This can be defined with entries in CodeMeter License Central that are completed when the license is activated. An adjustment to the WebDepot license portal or the software activation assistant and gateway allows the name to be overwritten upon each activation.

To change the user name, the license is deactivated and reactivated with a new user name.