User Resource Calendar Login Restrict
Make sure your team only signs in during the hours they're actually scheduled to work. This module checks each user's standard Odoo Resource Calendar at the exact moment of login and blocks access outside those working hours - with no restriction at all for users who don't have a calendar assigned.
Key Features
-
Restrict login to working hours
-
Built on standard Resource Calendar
-
Simple per-user assignment
-
No calendar means unrestricted login
-
Real-time check
-
Leave records don't block login
-
Timezone-aware enforcement
-
Clear login-denied message
-
No new models or menus
-
Reuses HR & Project schedules
Automatic Working-Hours Enforcement
Every login attempt is checked the instant credentials are verified. If the signed-in user's Resource Calendar says they're off the clock right now, the session is refused before it ever starts.
- Runs on every login, with no extra step for users
- Evaluated against the exact second the login happens
- Denied logins never reach the Odoo backend
Built on the Standard Resource Calendar
No new working-hours model to learn. The module reads the same Resource Calendar used by Employees, Project, Manufacturing, and other Odoo apps, so schedules you already configured just work.
- Reuses calendars you may have already set up
- Supports as many working schedules as your company needs
- Full flexibility of attendance lines, breaks, and days off
Safe by Default - No Calendar, No Restriction
Assigning a calendar is entirely optional. Users with no Resource Calendar set keep logging in exactly as before, so you only turn the restriction on for the accounts that need it.
- Nothing changes until you assign a calendar
- Roll out gradually, team by team or user by user
- Clear the field anytime to lift the restriction instantly
Real-Time Checking
The check looks at the exact current instant using the calendar's work-hours count, not a cached daily flag, so access opens and closes precisely on schedule - in the calendar's own timezone.
- Evaluated fresh on every single login attempt
- Honors the calendar's configured timezone
- Only the schedule matters - approved leave doesn't affect it
One New Field on the User Form
Setup takes seconds. The module adds a single Login Working Hours section to the existing user form, right in the Preferences tab administrators already know.
- One dropdown: pick a Resource Calendar
- No wizards, no separate configuration screen
- Change or clear it anytime, effective from the next login
Go to Settings -> Technical -> Resource -> Working Schedules and open or create the schedule that matches your team's hours: attendance lines for each working day plus the correct timezone. If you already use resource calendars in Employees or Project, you can reuse those schedules directly.
Open Settings -> Users & Companies -> Users, select a user, and on the Preferences tab find the new Login Working Hours group. Pick the schedule in the Resource Calendar field and click Save. Repeat for every user you want to restrict.
Log out and sign back in while inside the assigned working hours to confirm access still works, then try again outside those hours to see the "Login denied" message. Leave the Resource Calendar field empty on any account, such as an administrator, that should never be restricted.
Frequently Asked Questions
Can't find your question? Contact us at hello@ekika.co or open a support ticket at ekika.co/support.
Nothing changes. If a user's Resource Calendar field is empty, login works exactly as it did before installing the module. The restriction only takes effect once a calendar is assigned to that user.
No. The check only looks at the working-hours pattern defined on the calendar, not leave or time-off records. A user who is on approved leave but still within their normal shift window can still sign in.
Yes. Each user is assigned their own Resource Calendar independently, so different teams or shifts can each have their own schedule, all enforced by the same check.
Yes. Simply leave that user's Resource Calendar field empty - they will always be able to log in without any working-hours restriction, regardless of the time.
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 | 525 |
| Technical Name |
ek_user_res_calendar_login_restrict |
| 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