Skip to Content
Menu

User-Based Automatic Screen Lock on Inactivity | Auto Lock Backend Screen Based on Idle Time

by
Odoo

231.46

v 18.0 Third Party
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Community Apps Dependencies
Lines of code 356
Technical Name screen_lock_user_auto
LicenseSee License tab
Websitehttp://www.probuse.com
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Community Apps Dependencies
Lines of code 356
Technical Name screen_lock_user_auto
LicenseSee License tab
Websitehttp://www.probuse.com

User Based Automatic Screen Lock on Inactivity

Auto Lock Backend Screen Based on Idle Time

This module introduces an automatic screen lock feature in the Odoo backend based on user inactivity. It enhances system security by locking the users screen after a defined period of idle time. Each user has a personal timeout setting that determines when their screen should lock. Administrators can define a default timeout globally, which is applied only when new users are created. The locking mechanism runs in real time using Odoos modern JavaScript framework, ensuring both performance and security.


Main Features:

  • User Specific Timeout Settings:
    • Each user has a configurable screen timeout setting (in minutes) available on their user profile.This defines how long the user can remain inactive before the screen locks.
  • Default Timeout for New Users:
    • Administrators can define a default timeout from Settings.
    • This value is only used as the initial timeout value when new users are created.
    • Existing users are not affected when the global setting is changed.
  • Automatic Screen Lock Triggered by Inactivity:
    • The system tracks user activity (mouse movement, clicks, keypresses).
    • When the user is inactive for their defined timeout period, the screen automatically locks.
  • Frontend Based Lock Logic:
    • Lightweight JavaScript logic runs in the background to detect inactivity.
    • It checks the last activity timestamp at regular intervals without affecting performance.
  • Session Info Integration:
    • The users timeout setting is included in the session data returned from the server.
    • This ensures each user receives their personalized timeout value.
  • Cookie Based Lock Check:
    • A browser cookie ensures the screen is not locked multiple times unnecessarily.
    • The system checks this before triggering a lock action.
  • Custom OWL Service:
    • Screen locking is handled by a dedicated OWL based service, allowing smooth frontend integration.
  • Multi Tab Behavior (Screen Lock in One Tab Locks Others):
    • When working in multiple browser tabs with the same user account, the auto lock system treats each tab independently.
    • For example, if a user has 3 open tabs and their timeout is configured to 5 minutes:
      • If the user is only active in one tab, but inactive in the other two,
      • After 5 minutes, the inactive tabs may trigger the lock screen and set the shared cookie is_screen_locked to true.
      • As a result, even the active tab will show the locked screen immediately on page reload or next session check.
    • This ensures security consistency across tabs, but may lead to unexpected locking if only one tab remains active.

Workflow:

  • Install the App:
    • Once installed, the auto screen lock feature is enabled across the system.
  • Set Default Timeout (Optional):
    • Go to Settings > General Settings and configure a default timeout (in minutes).
    • This default will be applied only when new users are created.
  • Manage Per User Timeout:
    • Edit each users profile to set or adjust their individual screen timeout.
    • This gives flexibility to tailor locking behavior by role or responsibility.
  • Screen Auto Locks:
    • After the user is inactive for the configured time, their screen will auto lock.
    • This action is triggered by the frontend based on the last activity timestamp.
  • Unlocking:
    • Users can unlock the screen as per the logic provided in the main screen_lock_user module (e.g., using a PIN or password reauthentication).

Edition Compatibility:


Enterprise Odoo.sh

Screen Timeout Duration (Minutes) : General Settings

Screen Timeout Duration (Minutes) : User Form View

Odoo Standard : User Preferences Menu

Screen Timeout Duration (Minutes) : User Preferences Wizard

Screen View : Display Before Timeout

Locked Screen View : Display After Timeout

Example 2

Odoo Standard : User Preferences Menu

Screen Timeout Duration (Minutes) : User Preferences Wizard

Screen View : Display Before Timeout

Locked Screen View : Display After Timeout

Contact / Support
Introducing Probuse Consulting Services Pvt. Ltd.

If you need any help or want more additional features, you may contact us through:
Email: contact@probuse.com
Website: www.probuse.com
Skype: mustufa_probuse

Probuse Consulting Service Pvt Ltd is an Software and Web development specialist which offers complete business application together. We are well experienced to provide a face for your business on the software and Internet level.

Probuse Consulting Service Pvt Ltd is a specialist in Odoo/OpenERP services and could give your business open source hand to drive.

Our Services

  • Odoo Implementation

  • Odoo Support

  • Odoo Customization

  • Odoo Migration

  • Odoo Training

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.