Portal Sale Confirm Require Login
This module enforces authentication when accessing quotations or sale orders from the portal, optionally depending on the module configuration, and requires the partner information to be completed before the order can be confirmed, signed, or paid.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds an option to force customers to log in before opening a quotation or sale order from a portal link, and blocks signing, accepting or paying until their contact details (phone, VAT, address, country) are complete.
This module changes how customers interact with quotations and sale orders on the customer portal.
A new setting appears in Sales settings: "Require Login To Access Portal Sale Documents". When enabled, a public visitor who opens a quotation or order link is redirected to the login page, or to a sign-up page if the customer has no user account yet. PDF, text and link-preview requests are still allowed without login.
Before a customer can accept, sign or pay an order from the portal, the module checks that the customer record contains phone, VAT, street, city and country. If the country requires a state, the state field is also required. When information is missing, the normal action buttons are replaced by a button that sends the customer to their account page to complete the details, then returns them to the order.
On the address form, the country field is locked once a country is set, and the VAT field is only editable when no VAT is recorded yet. The module touches sale.order, res.partner, res.config.settings and the portal order page.
Depends on
Models and fields (3)
- sale.order · extends an existing model
- res.partner · extends an existing model
- res.config.settings · extends an existing modelportal_sale_access_login_required (Require Login To Access Portal Sale Documents)
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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/sale-workflow.
terminal Installation and usage
OCA documentation · Odoo 19.0Configuration
Source · Odoo 19.0To configure this module, go to Sales > Configuration > Settings and review the Require login to access portal sale documents option under Quotations & Orders.
This option is disabled by default.
- Enabled: public users must log in before accessing quotations or sale orders from portal links.
- Disabled: public users can access those documents from portal links, but authentication is still required to confirm, sign, or pay them.
Usage
Source · Odoo 19.0- Send a quotation to the customer or share the portal link containing the access token.
- When the customer opens the quotation from the portal:
- If the customer is not logged in and a portal user already exists for the related partner, they are redirected to the login page.
- If the customer is not logged in and no portal user exists yet, they are redirected to the signup page using a secure signup token.
- After logging in or completing the signup process, the customer is redirected back to the quotation in the portal.
- Before the quotation can be accepted, signed, or paid, the system checks that the partner linked to the sale order has all required information completed.
- If required partner information is missing, the customer is prompted to complete it before continuing.
- Once authentication and partner information requirements are satisfied, the standard Odoo confirmation, signature, and payment flow proceeds normally.
No verified information in OCA: Installation.
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.