Understand licensing for NVivo Server

NVivo Server 11 R2

This topic is about licenses for NVivo Server. To work with NVivo projects stored on a server, your organization needs licenses for both NVivo for Windows and NVivo Server. For more information about licenses for NVivo 12 (Windows) refer to Understand licensing for NVivo.

Overview of NVivo Server licensing

NVivo for Windows and NVivo Server are separate software products. To work with NVivo projects stored on a server, your organization needs licenses for both NVivo for Windows and NVivo Server.

A license key is required to install NVivo Server on the server. In addition, each client machine needs an NVivo for Windows license key. For information about client licensing, refer to Understand licensing for NVivo.

NVivo Server licensing arrangements are tailored to meet your organization’s needs. The licensing is based on the number of users that need to connect to server projects.

When users connect to a server project, they consume Client Access Licenses (CALs). You can choose to allocate license to specific users, or to concurrent (floating) users, or a combination of both.

Understand how server licenses work

Depending on the terms of purchase, your NVivo Server license key:

  • Entitles you to run NVivo Server on a server

  • Entitles you to a number of Client Access Licenses (CALs) that allow users to access server projects.

NVivo Server supports multiple active license keys, as shown in the example below:

 

Client Access Licenses (CALs) can be distributed among:

  • Named users—specified user accounts (not groups) that have 1 CAL reserved for their specific use. These user accounts have a guaranteed server connection at all times.

  • Concurrent users—user accounts that do not have any CALs reserved for their use.  These user accounts require 3 CALs each. Concurrent or ‘floating’ users connect to NVivo Server on a first-come, first-served basis. A concurrent user can only connect if there are available CALs.  

By default, Client Access Licenses are not allocated to specific users—users can connect to a server project if there are available CALs. However, if some of your users need guaranteed access to the server then you can allocate a CAL to them so that they can always connect. Refer to Understand user access and Manage user access to the server for more information.