Crm Tag Multi Company Event CRM
Ensure multi-company check in event lead rules tag ids.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Keeps event lead rule tags limited to the companies the user is allowed to work with, so tags from other companies cannot be selected on event lead rules.
This module is a small compatibility bridge between the CRM tag multi-company feature and the Event CRM lead generation rules. It changes how the tags field on event lead rules behaves when several companies are used in the same database.
- On the event lead rule screen, the tag field (
lead_tag_ids) now applies a company check. This means only tags that belong to the companies the user is allowed to access can be chosen. - The rule is enforced automatically by Odoo whenever the field is used, so no extra button or menu is needed.
- It touches the
event.lead.rulemodel, which is the model behind the rules that automatically create CRM leads from event registrations. - The module installs itself automatically when both the CRM tag multi-company module and the Event CRM module are present, so users do not have to install it manually.
There are no new menus, reports, scheduled actions or emails in this module. Its only visible effect is that the tag selection on event lead rules respects company boundaries, preventing users from mixing tags that belong to companies they cannot access.
Depends on
Models and fields (1)
- event.lead.rule · extends an existing modellead_tag_ids
Text generated by AI (DeepSeek) from reading the Odoo 16.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: 1 confirmed, 8 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.