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.
In this topic
To set up NVivo for Teams requires 2 licenses:
A license for NVivo for Teams (NVivo 11 R2) Server. This includes the number of client access licenses (CALs) that the organization has purchased. CALs determine the number of user connections that can be made to the server.
An enterprise license for NVivo (Windows) client software. This is for a specified number of user seats (however many the organization bought)—i.e. concurrent users of the NVivo desktop client.
So, for example, an organization might buy 1 license for NVivo Server (allowing installation of 1 instance of the server), with 50 CALs, allowing 50 users to connect to the server at once. If they also buy an NVivo client enterprise license for 100 seats, then 100 users can be on the clients at once, but only 50 of them can connect to the server at once.
To install, NVivo Server requires a license key, supplied with the purchase.
NVivo client software may or may not require a license key:
NVivo version 12 and earlier requires a license key. Under an enterprise license agreement, 1 license key serves for all user seats under the license.
Most installations of NVivo release 1 client software do not require a license key—instead, end users activate each installation using their personal myNVivo accounts. Under one installation strategy, however, organizations' IT departments install and activate the clients for users, in which case a license key is used. See Understand licensing for NVivo.