It depends on the deployment: 

Normal connected-to-the-server use : When a user starts the product, the computer requests a permit from the server. While the permit is allocated, that permit cannot be used by anyone else until it is RETURNED to the pool. When the user closes the product, the permit is made available for use on another computer again. 

Borrowing from a server & Borrowing remotely: In the 'borrowing' scenario, a permit is allocated to the computer for a time period, ranging from one day up to FIVE years. The advice is always to set a SENSIBLE 'borrowing' period. For example, if the user is working remotely for seven DAYS, set the period for seven days. 

It depends on the deployment: 

Normal connected-to-the-server use : When a user starts the product, the computer requests a permit from the server. While the permit is allocated, that permit cannot be used by anyone else until it is returned to the pool. When the user closes the product, the permit is made available for use on another computer again. 

Borrowing from a server & Borrowing remotely: In the 'borrowing' scenario, a permit is allocated to the computer for a time period, ranging from one day up to five years. The advice is always to set a sensible 'borrowing' period. For example, if the user is working remotely for seven days, set the period for seven days.