...
Starting from version 1.6.5, users will have access and treated as active until the end of the configured threshold period. However, they will immediately lose access after this after the treshold time, and the LO app will not extend the expiration time . The user can regain access and users will treated as inactive users immediately and their seats can be freed up for others. These users will not lost their access after the static treshold period, they will be only treated as inactive, and they can regain a new active period if a subsequent request is made, depending on seat availability.
Example
Threshold: 1 hour (60 minutes).
...
First request/activity: User has access from 10:00 to 11:00.
Second request/activity: User becomes active at 10:05, and the expiration time is updated to 11:05.
Third request/activity: User becomes active at 10:10, and access is extended until 11:10.
The User does not send any new request, and LO treat it as an inactive user after 11:10, and its seat can be freed up for a new user that needs access.
After version 1.6.5:
First request/activity: User has access from 10:00 to 11:00.
Second request/activity: User becomes active at 10:05, and the expiration time remains at 11:00.
Third request/activity: User becomes active at 10:10, and the expiration time remains at 11:00.
After 11:00, the user will receive a notification indicating that their access has been revoked and needs to be renewed.
If there are empty seats at 11:00 or 11:01, the user will regain access.
If there are no empty seats, the user will need to wait until a seat becomes available if someone else has been granted access ahead of them
LO treat it as an inactive user and its seat can be freed up for a new user that needs access.