Idle Session Logout
Idle Session Logout automatically ends a session the moment a user goes inactive beyond their own allowed limit. Each user gets a personal idle timeout, enforced silently in the background every two minutes â no browser scripts, timers, or pop-ups required. Built directly on top of User Session Management, it clears the session, the server-side session cache, and the session record all at once.
Key Features
-
Per-user idle timeout minutes
-
One-click enable per user
-
Checks every 2 minutes
-
True logout, not a flag
-
Clears server-side session cache
-
Independent per device/browser
-
Batch-safe for large teams
-
Built-in validation guardrails
-
Extends User Session Management
-
No client-side script needed
Per-User Idle Timeout
Every user gets an Allow Idle Time Logout toggle and their own Idle Logout Minutes value, right on the standard user form. Different teams can carry different limits without touching a single line of code.
- Enable per user, not globally
- Supports fractional minutes
- Field is required only when enabled
Validation Guardrails
A model constraint stops misconfiguration before it happens: minutes can never go negative, and idle logout can't be enabled with zero minutes set, which would otherwise log a user out instantly.
- Blocks negative timeout values
- Requires a positive value when enabled
- Clear, actionable error message
Evaluated Per Device
Idle time is checked per session, not per user. A user actively working on their desktop keeps that session alive even if a forgotten mobile browser session goes idle and gets logged out on its own.
- Each device/browser tracked separately
- Active sessions are never touched
- Works with unlimited concurrent sessions
Go to Settings -> Users & Companies -> Users and open the user you want to protect. Scroll to the Preferences tab, where a new Idle Session Logout group appears right beside the existing User Session Manage group.
Toggle Allow Idle Time Logout on. The Idle Logout Minutes field appears and becomes required â enter how many minutes of inactivity this user is allowed before their session is ended (defaults to 15).
Click Save. From this point on, the Logout Idle Sessions scheduled action checks this user's sessions every 2 minutes and ends any session whose last activity is older than the configured limit â automatically, with no further action needed.
Step 4 - (Optional) Adjust the Check IntervalTo check more or less often, go to Settings -> Technical -> Automation -> Scheduled Actions, open Logout Idle Sessions, and change the Interval Number and Interval Unit. The default is every 2 minutes.
Frequently Asked Questions
Can't find your question? Contact us at hello@ekika.co or open a support ticket at ekika.co/support.
No. Idle Logout Minutes is set per user, so different roles or departments can carry different limits.
Every 2 minutes by default, via the Logout Idle Sessions scheduled action. Admins can change the interval under Settings -> Technical -> Automation -> Scheduled Actions.
No. Idle time is evaluated per session, so only the inactive session on that specific device or browser is ended â the active session is left untouched.
Yes. Simply leave Allow Idle Time Logout unchecked for that user â they keep whatever session-expiry behavior is already configured by User Session Management.
Yes, the module works on both Community and Enterprise editions of Odoo.
Contact us:
- WhatsApp / Phone: +919510031431 - URGENT
- Email: hello@ekika.co
- Website: https://ekika.co
- Support Ticket: https://ekika.co/support
- 24 x 7 Available - Contact us NOW.
Need Help?
EKIKA Has Your Back - 24/7 Support.
We're just a message away, no matter the time zone.
90 Days Free Support
(copy link to clipboard)
(copy link to clipboard)
(copy link to clipboard)
Services EKIKA Provides
EKIKA is your destination for expert Odoo ERP implementation and customization. We pride ourselves on building reliable, trust-based partnerships that give you full transparency and control over your business processes.
With over 12 years of experience, we can assist you with eCommerce platforms, production planning, point-of-sale systems, inventory management, and advanced field worker tracking solutions to optimize your workflows.
Implementation
Odoo ERP tailored for your business needs for smooth operations.
Customization
Personalized adjustments to Odoo modules for seamless management.
Support
Ongoing assistance and maintenance to keep your Odoo running smoothly.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Community Apps Dependencies | Show |
| Lines of code | 580 |
| Technical Name |
ek_idle_session_logout |
| License | OPL-1 |
| Website | https://ekika.co |
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