About named user and concurrent login licensing

A named user license links one user login to one license through the User Modules form. For example, if you plan to have three users, such as bobw, jeanp, and miker, that run Mongoose, you must request three named licenses.

Unless you have a usage-tracking license, named license users are only allowed one active login to a Mongoose site, and that login consumes a license. If you try to log in a subsequent time as a named user who holds an active session, Mongoose requires the active session to be released. However, there are two exceptions to this:

• If you have a usage-tracking license, you can have multiple users logged in, limited only by the number of licenses you purchased on your agreement.
• If you have a special multi-session user provided as part of your license, that user can have multiple logins and sessions.

With named user licensing, when you associate a user with a license module, Mongoose verifies that there are remaining tokens for the module not yet associated with a user. A license module token is consumed at the time the user is assigned to that module. If a license module assignment is later removed from a user, that license module token is returned to the pool of available tokens. When the user logs in and attempts to access a form or IDO, Mongoose verifies that the user is associated with at least one license module containing the resource.

In a multiple-sites-per-database environment, each named user can log in once per shared site, which counts as one license token against each module to which that user is assigned.

Again, if you have a usage-tracking license, this is rule is bypassed.

With concurrent login licensing, licenses are assigned to users, but the license check does not occur until users log in. If the number of users logged in to a site with a particular license module is equal to the license number limit, and another user tries to log in, that user is not allowed to log in to the site. Using the same example, if you have two concurrent Mongoose licenses, you can assign that license to three users (bobw, jeanp, and miker). However, only two of them can use the Mongoose license token at a time.

The reverse is also true. For example, miker is assigned concurrent licenses for Mongoose and ServiceManagement, so he can work in both functional areas while he is logged in.

Under concurrent licenses, a user can log into a certain site multiple times, as long as the total number of license tokens currently consumed in Mongoose for any module that applies to that user is less than the licensing limit for that module in that site. A module applies to a user if that module is assigned to that user and has the same session type as the user's connection, or has an Undefined session type.

With concurrent login licensing, you can associate as many users as you want with a module in a site, regardless of how many tokens you have purchased for the module. When a user logs in, Mongoose verifies that there are remaining tokens for each of the modules or session types that apply to that user, and then consumes a token for each of those modules for the duration of that user's session. License module tokens consumed during a user’s session are returned to the available pool when the user logs off.

Again, this rule is bypassed if you have a usage-tracking license. In this case, no tokens are consumed or counted.