This module allows to restrict access to specific website pages to logged users.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets you mark specific website URL paths as private so that only logged-in users can open them; visitors are sent to the login page first.
This module adds a simple list where you decide which parts of your website require a login. You can find it under Website configuration, in the menu "Authorization required URLs". There you add one line per website and per URL path, for example /shop. The same path cannot be added twice for the same website.
When a visitor opens a page, Odoo checks the requested URL against that list. If the URL matches an entry, or is a sub-page of it (for example /shop/product when /shop is listed), the visitor is redirected to the login page and then back to the page they wanted. Public pages that are not in the list stay open as usual.
- Applies per website, so different websites can have different private areas.
- Covers the path and everything below it.
- Logged-in users are not blocked.
- The website's own public user is still treated as a visitor, so it is also redirected.
It works by extending the website request handling (ir.http) and stores the rules in a new model, website.auth.url, with fields for the website and the path. Only website designers can manage these entries.
Depends on
Menus it adds
Models and fields (2)
- ir.http · extends an existing model
- website.auth.url · new modelpath, website_id
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/website.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0Website \> Configuration \> Authorization required URLs: select a website and enter a relative path, eg: /shop
When public user will try to access mywebsite.com/shop or any of its child pages, they will be requested to login.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.