Geo Fence Login Restrict
Geo Fence Login Restrict locks down who can sign in to Odoo based on where they physically are. Define geo-fence zones by latitude, longitude and radius, then mark them as allowed or restricted for individual users or entire companies â Odoo checks the browser's live GPS location against those zones before granting access. A built-in rescue user and portal bypass mean you can never lock yourself out.
Key Features
-
Restrict login by real GPS location
-
Per-user allowed & restricted fences
-
Per-company allowed & restricted fences
-
Configurable radius per fence, meters
-
Dedicated GEO Fence Rescue User
-
Skip geo-fencing for portal users
-
Live browser geolocation on login
-
Login history logs GPS coordinates
-
Blocks access on denied location
-
Built for User Session Manage app
-
On-screen location status messages
-
Safety check before first fence
-
Multi-company geo-fencing supported
-
API and RPC logins unaffected
-
Simple list & form fence manager
Geo Fence Zones
Create named geo-fence zones by pinpointing a center latitude/longitude and a radius in meters. Every zone is validated automatically so coordinates and radius always stay within a valid range.
- Latitude/longitude with 8-decimal precision
- Custom radius per zone, in meters
- Enable/disable zones anytime via Active toggle
User-Level Access Control
Assign allowed or restricted geo fences directly on a user's profile. Allowed fences act as a whitelist; restricted fences act as an instant blacklist that always wins.
- Many2many "Allowed Geo Fences" per user
- Many2many "Restricted Geo Fences" per user
- Restrictions always override allowances
Company-Level Access Control
Apply the same allow/restrict logic at the company level so every user of that company is covered without configuring each profile individually. User and company fences are combined automatically.
- Company-wide allowed & restricted zones
- Combines with user-specific fences
- Ideal for multi-company deployments
Live Location Capture at Login
The login page asks the browser for the visitor's GPS coordinates the moment it loads, using the standard Geolocation API. A friendly status message keeps the user informed while location resolves.
- Runs automatically, no extra clicks
- Works over HTTPS in all modern browsers
- Clear status for granted, denied or unsupported
GEO Fence Rescue User
Every deployment needs an escape hatch. Marking a user as a GEO Fence Rescue User lets them log in from anywhere, and the system refuses to save a single geo fence until at least one rescue user exists.
- Bypasses all location checks for that user
- Creating geo fences is blocked without one
- Prevents accidental company-wide lockouts
Portal User Bypass Setting
Customers and portal contacts usually don't need geo-fencing. A single Settings toggle lets portal users sign in from any location while employees stay fully restricted, and it's enabled by default.
- One checkbox in Settings -> Users & Companies
- Applies to portal (base.group_portal) users only
- Enabled out of the box, disable anytime
Login History with Location Tracking
Every login attempt captured through the geo-fence flow records its latitude, longitude and accuracy alongside the existing session log, giving admins a full audit trail of where logins came from.
- Extends the User Login History list
- Stores GPS accuracy in meters
- Useful for security audits and investigations
Before you configure anything else, protect yourself from an accidental lockout. Go to Settings -> Users & Companies -> Users, open the user who should always be able to log in (typically an administrator), scroll to the new Geo Fence group, and enable GEO Fence Rescue User. Save the record â the system will not let you create a single geo fence until at least one rescue user exists.
Go to Settings -> Users & Companies -> Geo Fences and click New. Give the zone a descriptive Name, enter its center point as Latitude / Longitude, and set the Radius (Meter) that defines how large the allowed circle is around that point. Save when done.
Open any user's form (Settings -> Users & Companies -> Users) and scroll to the Geo Fence group. Add zones under Allowed Geo Fences â the user must be inside at least one to log in â and/or Restricted Geo Fences â the user is always blocked from inside these, even if also allowed elsewhere.
To cover every user of a company at once, open Settings -> Users & Companies -> Companies, select the company, and add zones under the new Geo Fence group on the General Information tab. User-level and company-level fences are combined automatically.
Go to Settings -> General Settings, find the User Session Manage section, and toggle Skip Geo Fencing For Portal Users. It is enabled by default so portal/customer logins are never blocked; disable it if portal users should also be geo-fenced.
Log out and log back in. The browser will ask for permission to share your location â grant it. If your coordinates fall inside a restricted zone, or outside every allowed zone, the login is rejected with a clear message; otherwise you're signed in as normal.
Open the account menu in the top-right corner and choose Login History (added by the User Session Manage app) to see every login attempt together with its Latitude, Longitude and Location Accuracy columns â a ready-made audit trail for security reviews.
Every login attempt runs through the same ordered set of checks, from the most permissive escape hatch down to the strict fence match. The first rule that applies wins.
GEO Fence Rescue User
Always allowed. Skips every other check â this is your permanent escape hatch.
Portal User + Bypass Enabled
Portal users log in without any location check when the Settings toggle is on.
No Fences Configured
If neither the user nor their company has any allowed or restricted fence, geo-fencing is simply inactive for them.
Inside a Restricted Fence
Always denied â a restricted fence overrides an allowed fence even if both match.
Allowed Fences Configured
The visitor must be inside at least one allowed fence, or the login is denied.
Otherwise, Allowed
No restricted match and no allowed fences to satisfy â the login proceeds normally.
Frequently Asked Questions
Can't find your question? Contact us at hello@ekika.co or open a support ticket at ekika.co/support.
If the user is covered by a geo fence (allowed or restricted) and their location status isn't granted, the login is rejected with a clear message asking them to allow location access and try again.
The module blocks that: a Geo Fence record cannot be created at all until at least one GEO Fence Rescue User exists, and that rescue user can always log in from anywhere.
Yes. If a user's current location falls inside any Restricted Geo Fence, access is denied immediately â even if the same location also matches an Allowed Geo Fence.
No. The location check only runs when the standard login form submits geo-fence data. External API/RPC authentication is not affected and continues to work as usual.
Yes. Allowed and Restricted Geo Fences can be configured on both individual users and on each company record, and the two are combined automatically â ideal for multi-company databases.
Not by default. The Skip Geo Fencing For Portal Users setting is enabled out of the box, so portal accounts can sign in from anywhere unless you turn it off.
It uses the device's native Geolocation API (GPS/Wi-Fi/network positioning) and calculates distance against the radius you set on each fence â typically accurate to within a few meters on GPS-enabled devices.
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 | 909 |
| Technical Name |
ek_geo_fence_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