QlikView checks for licenses in the following order: Named Cal Document Cal Session Cal Usage Cal
You may have a mixture of the above licenses or only some of them, depending upon which QlikView product you are using and which version you are using.
Named Cal (assigned to a specific user ) can open and work on QlikView applications (documents) on and offline and open as many documents as they wish (security allowing) - the license can be psychically installed on a specific machine (developers machine maybe) , or leased (not allowed in test environment) for 30 days after which, the users needs to access QlikView on the server to renew their license.
Doc Cal allows 1 user to open one application or one document (online only), they can be in the document for as long as they wish, but once they close the document, the document license is gone (its goes back into a pool of Documents Cal ). If you open a different application, you use another document cal.
Session Cal are similar but not identical to Named Cal (these are for rolling access to many QlikView applications (they work like a named CAL except, they are not attached to a specific user) I have only seen these used on-line. If you need to support 10 concurrent users accessing 5 QlikView applications, however, the 10 concurrent users change all the time, you could use 10 session Cal to support these users.
Usage Cal are your anyone else who occasionally needs to access a specific document maybe a month end or year end. You could use these CAL to catch anyone, who doesn't have any of the above licenses to provide access to QlikView.
Named and Doc Cal can be granted/allocated to specific users through the QMC. Alternatively, you can setup dynamically allocated Cal (Named or Document) , as a user logs in the receive a license automatically (not in TEST environment) . Some customer like to grant access to Named Cal to specific users (developers, super users document chained application users etc), then provide document Cal to the users automatically from the pool.
