License Pools are containers for the products, quantities, usage terms and usage restrictions for your Customers and their End Users.
The First thing you will want to do after a Customer's Account is created is create a License Pool. License pools are where you establish which products, terms and quantities will be accessible by your Customer and their End Users.
Follow the instructions beginning with Step 4 for creating a license pool.
Licenses have their own expiration date, which is set by Simplified Logic Sales. That expiration date is the day the server will stop serving those licenses. The Valid Until Date should be set to reflect the agreement you have with your customers irrespective of your license expiration dates in Nitro-LM. If the valid until date is sooner than your license expiry date, licenses will stop serving for this particular pool sooner. If the valid until date comes after your license expiry date, licenses will ignore that and stop serving on your license expiry date unless your Nitro-LM account is renewed. This feature allows you to keep track of when individual customers of yours are coming due for renewal irrespective of when your Nitro-LM licenses actually expire.
This is the Maximum number of days you want to allow a product to be checked out from the Nitro-LM server. This setting only applies to Checked-Out Licenses. Because Checked-Out Licenses are locked to a particular user until the checkout period ends, customers may start running out of licenses in their pool if users check licenses out for excessively long periods. This setting helps prevent that from happening for a specific Product within a Specific License Pool.
The Max Number of Licenses allows you to instruct Nitro-LM to only allow certain quantities of a particular Product to be used by Customers and End Users. This capability is most commonly applied when you have a License Pool with more than one Product being served from it. For Example: Product A and Product B are both in a license Pool with 10 Licenses. If you have no "Max # of Licenses" set, customers can use any combination of Product A and Product B up to the max number of licenses (10 in this case). If you set Product A to have Max Number of Licenses set to three (3) - then Product B could be used all the way up to 10 licenses concurrently, but Product A could only be used up to a MAXIMUM of 3 Licenses within the License Pool. One reason for doing this is to ensure that no matter how many licenses of Product A are issued, there will ALWAYS be 7 license slots available for Product B.
You do have the ability to control access to the License Pool - this is disabled by default. To Activate it, simply select the "Access Restrictions" tab..
You can limit access to the pool in a number of ways. You can restrict by Domain (most common method) or by individual End User e-mails.
Domain Restriction - This is a generic catch-all requirement for users to gain access to the License Pool's content. If you put in an include domain restriction, Nitro-LM will NOT allow anyone whose e-mail address does not match the restriction to have access to the Licenses controlled by the Pool; if you put in an exclude domain restriction Nitro-LM will not allow anyone whose email address DOES match the restriction to have access. In both cases, exceptions to domain restrictions can be granted using the Email Restrictions.
Email Restrictions - you can do selective include/excludes of specific users within the Nitro-LM system. For example, you may only want one (1) or two (2) users to have access to a specific product(s) in a License Pool (kind of like dedicating licenses to specific users). Alternatively, you may want to apply a Domain Restriction first, then so selective includes for users that do not match the domain restriction (or selective excludes for users that DO match the domain restriction but you still want to prevent their access for some reason).
The combination of Domain Restrictions and eMail restrictions is very (very) powerful!
License Queuing was created to streamline the sales process by allowing customers to self-govern their license usage without bothering your sales people every time "No More License" events were generated/triggered.
This feature is best used for customers that try to get by with less software than they need. For Example a 50 user organization tries to share 5 license of software. Normally this would cause a lot of "No More License" Notification events as a result of the disproportionate number of users to purchased licenses. However, you can implement License Queuing to get around this.
License queuing will automatically notify the customer directly in your software that "No More Licenses are Available..." and will also ask "Would you like to Queue a License Request?" If the user says NO, then the license will not be served and they are left right were they were right before the attempt. If they do say YES - then the server will try to Queue a License Request for them automatically. When a license becomes available, the user's Queued License Request will be automatically put into the available slot by the Nitro-LM Server - and the User will notified of its availability for their use.
If the user does NOT get the license, the Server will automatically purge the license and either allow another Queued License Request to take the slot, or make it available for other users to access. The settings for timeout of the license before it is freed is configurable via the Administration Interface.
License Pools by default are not active, this is to give the Licensee Administrators the opportunity to properly set it up and configure it without Customers and End Users trying to access it.