OdooWiki OCA HUB

Sale No Portal Button

sale_no_portal_button folder_open OCA/sale-workflow open_in_new
Uncategorised License: AGPL-3

Odoo Core shoehorns portal functionality into the sale module, which might not be what you want. Any time you use the chatter on a sale order, an email will be sent to the client (partner_id), with a button displaying access to this sale order. This module hides that button, and only displays it for contacts that have a user associated with them

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

This module removes the button that gives customers access to the sale order in the customer portal from sale order notification emails, except for contacts that have a user account.

When you send a message from the chatter of a sale order, Odoo normally includes a button in the email that lets the customer open the sale order in the portal. This module changes that behaviour.

  • For sale orders that are not in draft or cancelled state, the portal access button is hidden in the notification email sent to the customer contact.
  • The button is still shown for contacts that have a user account associated with them, so internal users can still access the order from the email.
  • The change applies to the sale order model (sale.order) and affects the notification recipients logic.

There are no new menus, screens, or settings. The module only modifies the email notification behaviour of sale orders.

Depends on

sale

Text generated by AI (DeepSeek) from reading the Odoo 18.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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

Sources · Odoo 18.0

Confirmed on 2026-11-03 in branch 18.0 of OCA/sale-workflow.

terminal Installation and usage

No verified information

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.

info

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.