This module add multi-company management to crm tag
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds a Company field to CRM tags so each tag belongs to a specific company. Users only see tags from their allowed companies (plus shared tags with no company), keeping CRM leads organised per company.
This module makes CRM tags company-aware. A new Company field is added to each tag, and it defaults to the company the user is currently working in. When a tag is deleted, its company link is removed as well.
Where it appears: - On the CRM tag form and list screens, a Company column/field is shown next to the colour, but only for users who have multi-company access enabled.
Business rules and automatic behaviour: - A record rule named "Crm Tag multi company rule" restricts which tags are visible: users only see tags whose company is one of their allowed companies, plus tags that have no company at all (shared tags). - Because the tag field on CRM leads is marked to check company consistency, Odoo prevents linking a lead to a tag that belongs to a different company.
Areas touched:
- crm.tag gains the company field and the visibility rule.
- crm.lead keeps its tag field but now enforces company consistency when tags are selected.
This is useful when several companies share one Odoo database: each company can maintain its own set of CRM tags without seeing or using the tags of the other companies, while still allowing some tags to be shared across all companies.
Depends on
Required by other modules
Models and fields (2)
- crm.tag · extends an existing modelcompany_id
- crm.lead · extends an existing modeltag_ids
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-03Confirmation 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 informationInstallation 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.