This module adds a partner and commercial partner field to activities
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Shows the related customer/contact and its commercial entity directly on activities, so you can see and search activities by partner without opening the linked record.
This module adds two extra columns to activities: the contact the activity is about and its commercial entity (the top-level company the contact belongs to).
- On every activity, the contact is filled in automatically: if the activity is linked to a contact, that contact is used; if it is linked to another record (for example a sales order or an invoice) that has a contact, that contact is copied onto the activity. If no contact can be found, the field stays empty.
- The commercial entity is taken from the contact's own commercial entity and is read-only, so it always follows the contact.
Where you see it: the activity form, the activity list, the activity kanban cards (the contact appears in the card title) and the activity search filters, all coming from the Activity Board screens. You can therefore filter and group activities by contact or by commercial entity.
The module only touches the activity model (mail.activity) and the contact model (res.partner) through the linked contact. It does not create new menus, reports or scheduled actions; it simply enriches the existing activity views with partner information.
Depends on
Models and fields (1)
- mail.activity · extends an existing modelpartner_id, commercial_partner_id (Commercial Entity)
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: 5 confirmed, 4 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/social.
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.