OdooWiki OCA HUB

Crm Lost Reason Multi Company

crm_lost_reason_multi_company folder_open OCA/multi-company open_in_new
Uncategorised License: AGPL-3

This module add multi-company management to crm lost reason

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Adds a Company field to CRM lost reasons so each company can keep its own list. Users only see and can pick lost reasons belonging to their allowed companies.

This module makes CRM lost reasons company-specific. Each lost reason now has a Company field, and when a user creates a new lost reason it is automatically assigned to the company they are currently working in.

  • On the lost reason form and list, the Company column is shown to users who work with several companies, so they can tell which company owns each reason.
  • A security rule limits visibility: users only see lost reasons whose company is one of their allowed companies (or reasons with no company set).
  • When a lost reason is selected on a lead or opportunity, Odoo checks that the reason belongs to the same company as the lead, preventing mismatched selections.
  • Deleting a company also deletes its lost reasons.

The module touches the CRM lost reason list and the lead/opportunity lost reason field. It does not add new menus or reports; it only extends the existing CRM screens and rules.

Depends on

crm
Models and fields (2)
  • crm.lead · extends an existing modellost_reason_id
  • crm.lost.reason · extends an existing modelcompany_id

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: 3 confirmed, 6 with no information of 9 versions.

Sources · Odoo 16.0

Confirmed on 2026-11-03 in branch 16.0 of OCA/multi-company.

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.