Odoo Changelog — 2026-02-02

Monday, February 2, 2026

4 changes · master

Bug Fixes(4)

Resolved issues and error corrections

[IMP] whatsapp: indicate access restriction on channel invitation link

EnterprisemasterdiscussMEDIUM

This update clarifies WhatsApp channel access restrictions for users. Now, a message displays below the invitation link, indicating which groups are allowed to join. This prevents confusion and ensures users understand who can participate in the conversation.

Original PR description

**Description of the issue this PR addresses:**
------------------------------------------------
Users had no clear indication when a WhatsApp channel was restricted to a specific access group.
This could lead to confusion about who was allowed to join the conversation through the invitation link.

**Current behavior before PR:**
---------------------------------
- The WhatsApp channel does not display any information about access restrictions.
- Users cannot easily understand why some people cannot join the conversation.

**Desired behavior after PR is merged:**
-----------------------------------------
- An explicit message “Access restricted to group ‘Role / User’” is displayed below the WhatsApp channel invitation link.
- Users can immediately understand that only members of the specified access group are allowed to join.

**Task:** 5135950

**Related Community PR:** https://github.com/odoo/odoo/pull/236226

#whatsapp#access#channel

[FIX] marketing_automation: make email from and reply to fields editable

PR #106091

Enterprisemastermarketing_automationMEDIUM

This update fixes an issue where users couldn't edit the 'Email From' and 'Reply To' fields when creating new email templates within marketing campaigns. The change restores the ability to modify these fields, ensuring users have full control over their email communications. This improves the flexibility and usability of the marketing automation features.

Original PR description

Currently when a user creates a new template from a marketing campaign, they can’t edit the `email_from` and `reply_to` fields, even though these should be editable in the template. **Steps to…

Currently when a user creates a new template from a marketing campaign, they can’t edit the `email_from` and `reply_to` fields, even though these should be editable in the template.

**Steps to replicate:**
* Install `marketing_automation`
* marketing automation > Create a New campaign > Add a new activity
* Mail template > Create a new template > Settings

**Observed Behavior:**
The fields `Send From` and `Reply To` are not editable which should be editable.

**Root cause:**
* After commit [1], the form view `mailing_mailing_view_form_marketing_activity` [2] was removed, so `email_from` and `reply_to` now come from the view [3]. Because that view inherits the `mass-mailing form`, its `readonly` rules apply (see [4]), and with `default_state` set to “done” (see [5]), those fields become `readonly` when creating a new mail template.

**Solution:**
Modify the readonly conditions to match how they were handled in earlier versions (see [6]).


**Before:**
<img width="1182" height="591" alt="image" src="https://github.com/user-attachments/assets/72006a7f-1ee5-40dd-8899-4eb932f503b7" />
**After:**
<img width="1182" height="591" alt="image" src="https://github.com/user-attachments/assets/d5d6bdf2-1fb6-4e7b-9527-412c44986050" />

[1]:
https://github.com/odoo/enterprise/commit/a469218b32943ddaa83271565e73311cfd188f84 
[2]:
https://github.com/odoo/enterprise/blob/97f6f87cca3939e48d3488672aba0df68acd8f9b/marketing_automation/views/mailing_mailing_views.xml#L75-L143 
[3]:
https://github.com/odoo/enterprise/blob/307b23b0f6b377c43463a04aabf0b2f03c256072/marketing_automation/views/mailing_mailing_views.xml#L107 
[4]:
https://github.com/odoo/odoo/blob/9e04aadb83d482d05fc2fa66fa3c3bebb6ac1528/addons/mass_mailing/views/mailing_mailing_views.xml#L328-L337 
[5]:
https://github.com/odoo/enterprise/blob/97f6f87cca3939e48d3488672aba0df68acd8f9b/marketing_automation/views/marketing_activity_views.xml#L23 
[6]:
https://github.com/odoo/enterprise/blob/97f6f87cca3939e48d3488672aba0df68acd8f9b/marketing_automation/views/mailing_mailing_views.xml#L96

opw-5401422,5449345,5369836

Forward-Port-Of: odoo/enterprise#101807

#marketing#email#templates

[FIX] delivery_starshipit: shipping method wizard

PR #105468

Enterprisemasterdelivery_starshipitMEDIUM

This update resolves an issue where users couldn't see all available Starshipit delivery services. The fix ensures Odoo sends complete order details to Starshipit, allowing users to accurately select the correct service based on their shipment information. This improves the user experience and ensures accurate delivery options.

Original PR description

Current behaviour:
Users are unable to select certain Starshipit delivery services. Delivery methods are configured in Odoo before address or package data is available. Since Starshipit requires this data to determine availability, it returns an incomplete list during setup.

Expected behaviour:
Users should be able to view and select from the complete list of valid delivery services based on the actual Sales Order details (address, weight, and volume).

Steps to reproduce:
1. Create new delivery method
2. Configure Starshipit API credentials.
3. Attempt to select a service.
4. Observe that not all service is shown from the available options.

Cause of the issue:
Starshipit filters services based on sender, receiver, and package info. Odoo requests the service list during initial configuration without this context, resulting in an incomplete list of methods.

Fix:
Introduce a mechanism in the Sales Order flow to add delivery methods. Send the complete shipment details (addresses, weight) to Starshipit to retrieve the accurate list of services and allow the user to select them.

Forward-Port-Of: odoo/enterprise#103316

#shipping#Starshipit#delivery

[FIX] ai_documents: traceback for users with access rights

PR #105947

Enterprisemasterai_documentsMEDIUM

This update resolves an issue preventing users with standard access rights from accessing the documents application. The fix restricts access to a sensitive field and limits visibility of certain features to system administrators, ensuring proper security and functionality for all users.

Original PR description

Internal Users with the "Access Rights" access right were not able to open the documents application, which raised an access error traceback on the `ai_sort_prompt` field - which has restricted access to only admins.

The access error was raised because the `ai_sort_prompt` field was added to the search_panel_fields for users with Access Rights access rights. We changed it so it is only added when users have the document system adminstrator role.

We also changed the document_service's start method to also define the documentSystem user which is the system adminstrator user. With that we could limit visibility of the System Prompt item in the cog menu to those users.

task-5375110

Forward-Port-Of: odoo/enterprise#105741

#access#security#documents

**Description of the issue this PR addresses:** ------------------------------------------------ Users had no clear indication when a WhatsApp channel was restricted to a specific access group. This could lead to confusion about who was allowed to join the conversation through the invitation link. **Current behavior before PR:** --------------------------------- - The WhatsApp channel does not display any information about access restrictions. - Users cannot easily understand why some people cannot join the conversation. **Desired behavior after PR is merged:** ----------------------------------------- - An explicit message “Access restricted to group ‘Role / User’” is displayed below the WhatsApp channel invitation link. - Users can immediately understand that only members of the specified access group are allowed to join. **Task:** 5135950 **Related Community PR:** https://github.com/odoo/odoo/pull/236226

Currently when a user creates a new template from a marketing campaign, they can’t edit the `email_from` and `reply_to` fields, even though these should be editable in the template. **Steps to replicate:** * Install `marketing_automation` * marketing automation > Create a New campaign > Add a new activity * Mail template > Create a new template > Settings **Observed Behavior:** The fields `Send From` and `Reply To` are not editable which should be editable. **Root cause:** * After commit [1], the form view `mailing_mailing_view_form_marketing_activity` [2] was removed, so `email_from` and `reply_to` now come from the view [3]. Because that view inherits the `mass-mailing form`, its `readonly` rules apply (see [4]), and with `default_state` set to “done” (see [5]), those fields become `readonly` when creating a new mail template. **Solution:** Modify the readonly conditions to match how they were handled in earlier versions (see [6]). **Before:** <img width="1182" height="591" alt="image" src="https://github.com/user-attachments/assets/72006a7f-1ee5-40dd-8899-4eb932f503b7" /> **After:** <img width="1182" height="591" alt="image" src="https://github.com/user-attachments/assets/d5d6bdf2-1fb6-4e7b-9527-412c44986050" /> [1]: https://github.com/odoo/enterprise/commit/a469218b32943ddaa83271565e73311cfd188f84 [2]: https://github.com/odoo/enterprise/blob/97f6f87cca3939e48d3488672aba0df68acd8f9b/marketing_automation/views/mailing_mailing_views.xml#L75-L143 [3]: https://github.com/odoo/enterprise/blob/307b23b0f6b377c43463a04aabf0b2f03c256072/marketing_automation/views/mailing_mailing_views.xml#L107 [4]: https://github.com/odoo/odoo/blob/9e04aadb83d482d05fc2fa66fa3c3bebb6ac1528/addons/mass_mailing/views/mailing_mailing_views.xml#L328-L337 [5]: https://github.com/odoo/enterprise/blob/97f6f87cca3939e48d3488672aba0df68acd8f9b/marketing_automation/views/marketing_activity_views.xml#L23 [6]: https://github.com/odoo/enterprise/blob/97f6f87cca3939e48d3488672aba0df68acd8f9b/marketing_automation/views/mailing_mailing_views.xml#L96 opw-5401422,5449345,5369836 Forward-Port-Of: odoo/enterprise#101807

Current behaviour: Users are unable to select certain Starshipit delivery services. Delivery methods are configured in Odoo before address or package data is available. Since Starshipit requires this data to determine availability, it returns an incomplete list during setup. Expected behaviour: Users should be able to view and select from the complete list of valid delivery services based on the actual Sales Order details (address, weight, and volume). Steps to reproduce: 1. Create new delivery method 2. Configure Starshipit API credentials. 3. Attempt to select a service. 4. Observe that not all service is shown from the available options. Cause of the issue: Starshipit filters services based on sender, receiver, and package info. Odoo requests the service list during initial configuration without this context, resulting in an incomplete list of methods. Fix: Introduce a mechanism in the Sales Order flow to add delivery methods. Send the complete shipment details (addresses, weight) to Starshipit to retrieve the accurate list of services and allow the user to select them. Forward-Port-Of: odoo/enterprise#103316

Internal Users with the "Access Rights" access right were not able to open the documents application, which raised an access error traceback on the `ai_sort_prompt` field - which has restricted access to only admins. The access error was raised because the `ai_sort_prompt` field was added to the search_panel_fields for users with Access Rights access rights. We changed it so it is only added when users have the document system adminstrator role. We also changed the document_service's start method to also define the documentSystem user which is the system adminstrator user. With that we could limit visibility of the System Prompt item in the cog menu to those users. task-5375110 Forward-Port-Of: odoo/enterprise#105741