| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Project (project) • Calendar (calendar) • Contacts (contacts) • Discuss (mail) |
| Lines of code | 96 |
| Technical Name |
codeerts_company_stages |
| License | LGPL-3 |
| Website | https://www.codeerts.com |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Project (project) • Calendar (calendar) • Contacts (contacts) • Discuss (mail) |
| Lines of code | 96 |
| Technical Name |
codeerts_company_stages |
| License | LGPL-3 |
| Website | https://www.codeerts.com |
| Versions | 17.0 18.0 19.0 |
Company-Wise Stages
Give every company its own CRM, Project and Helpdesk stages.
Keep shared stages for everyone, hide the rest per company.
Each company sees only its own pipeline columns and stage dropdowns. Single-company databases are unaffected.
|
3
Apps Covered
|
Per Company
Stage Pipelines
|
Shared
Stages Stay Global
|
0
Code Required
|
19.0
Version
|
The multi-company problem every admin knows
One shared set of stages for every company
|
Every company sees every stage
CRM, Project and Helpdesk stages are shared database-wide. A branch that only needs three stages still sees every other company's stages in its kanban and dropdowns. |
Cluttered, confusing pipelines
Sales and support teams scroll past columns that do not belong to their company, and someone eventually moves a record into the wrong company's stage. |
No way to separate by company
Odoo scopes stages by sales team, project or helpdesk team, but not by company, so franchises and subsidiaries cannot keep their own pipeline. |
What this module does
Company-Wise Stages adds a Company field to CRM stages, Project task stages and Helpdesk stages. Set a company on a stage and it becomes visible and usable only when that company is active. Leave the company blank and the stage stays shared with everyone, exactly as Odoo behaves today.
The filtering applies everywhere a stage appears: the kanban columns, the stage dropdown on the record, and the stage configuration lists. Each company works in its own pipeline plus the shared stages, without seeing the others. Helpdesk support installs automatically when the Helpdesk app is present.
|
🏢
A pipeline per company
Assign a company to any stage and only that company sees it. Each branch or subsidiary manages its own CRM, project and support flow. |
🔗
Keep shared stages
Leave a stage without a company and it stays global, visible to all. Mix a common backbone of shared stages with extra stages per company. |
✅
Nothing to configure
The Company field appears only in multi-company mode. Existing stages stay shared until you choose to assign a company. Single-company databases are unchanged. |
See it in action
From assigning a company to a stage, to a clean per-company pipeline.
CRM stages with a Company column: shared stays blank, company-only stages are tagged
Project task stages the same way: assign a company or keep the stage shared with every project
Open any stage and set its Company, or leave it blank to keep the stage shared with all companies
Everything included
|
📇 Company on every stage type
A Company field is added to CRM stages, Project task stages and Helpdesk stages. |
🔗 Shared stages supported
A stage with no company stays global and is visible to every company alongside its own stages. |
|
🗂 Kanban columns filtered
The pipeline shows the active company's columns plus the shared ones, never another company's stages. |
🔍 Dropdowns and lists filtered
The stage dropdown on the record and the stage configuration screens filter to the same set. |
|
🎯 Helpdesk bridge auto-installs
When the Helpdesk app is present, a bridge installs automatically and adds the same behavior to Helpdesk stages. |
🛡 Safe and non-intrusive
No change for single-company databases. The Company field shows only in multi-company mode, and existing stages stay shared. |
How it works
1 |
Install the module It adds a Company field to CRM stages and Project task stages. The Helpdesk bridge installs by itself when Helpdesk is present. |
2 |
Open the stage configuration Go to CRM, Project or Helpdesk Configuration and Stages. A Company column is now shown in multi-company mode. |
3 |
Assign a company or keep it shared Set a company on the stages that belong to one company, and leave the common ones blank to share them with everyone. |
4 |
Work in a clean pipeline Each company now sees only its own stages plus the shared ones, in the kanban, the dropdowns and the configuration screens. |
Technical information
|
Version
19.0
|
License
LGPL-3
|
Editions
Community & Enterprise
|
Dependencies
CRM, Project
|
Technical name: codeerts_company_stages · Helpdesk support: auto-installed bridge when Helpdesk is present
Frequently asked questions
Open CRM Configuration and Stages, edit a stage and set the Company field. That stage then appears only when the chosen company is active. Stages with no company stay shared with every company.
Yes. Any stage left without a company is treated as a global stage and stays visible and usable in every company, alongside that company's own stages.
Yes. The same Company field is added to CRM stages, Project task stages and Helpdesk stages. Helpdesk support installs automatically when the Helpdesk app is present.
Yes. The kanban columns, the stage dropdown on records and the stage configuration lists all filter to the company you are working in plus the shared stages, so other companies' stages are not shown.
No. With one company nothing changes. The Company field is shown only in multi-company mode, and existing stages stay shared until you assign a company.
Use the version selector at the top of this page to pick your Odoo release. The module runs on both Community and Enterprise, and each Odoo Apps Store listing shows the exact version it supports.
The team behind this module
About CODEerts
Full-Service Odoo ERP Agency · Solutions That Scale
Every module in our store is built from real client work, tested in production and maintained long-term by a team of Odoo certified consultants. When you need more than an app, we deliver the full solution.
|
🏗️ Implementation
Full Odoo roll-outs from requirements to go-live, across any industry and company size. |
🧩 Custom Development
Bespoke modules, OWL components and business logic built precisely to your workflow. |
🔄 Migrations
Zero-data-loss upgrades from older Odoo versions with full custom module porting. |
|
🔌 Integrations
Payment gateways, shipping carriers, biometric devices, eCommerce and third-party APIs. |
🔍 Odoo Audits
Performance, security and code-quality reviews that surface risks before they become problems. |
🧑💻 Support & Training
Ongoing helpdesk, user training and monthly retainers so your team stays productive. |
Please log in to comment on this module