Warning found in logs:
2026-01-16 17:23:12,813 43 WARNING 04464-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;button&gt;</tt></b> are displayed, but they depend on the field <b><tt>is_trusted_bank_account</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “is_trusted_bank_account” is accessible for groups: &#39;hr.group_hr_user&#39;<br/>- element “&lt;button title=&#34;Untrust Bank Account&#34; class=&#34;icon-button button-on&#34; icon=&#34;fa-solid fa-toggle-on fa-lg&#34; type=&#34;object&#34; name=&#34;action_untrust_bank_accounts&#34; invisible=&#34;not is_trusted_bank_account&#34;/&gt;” is shown in the view for groups: &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-16 17:27:13,204 43 WARNING 04464-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;button&gt;</tt></b> are displayed, but they depend on the field <b><tt>is_trusted_bank_account</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “is_trusted_bank_account” is accessible for groups: &#39;hr.group_hr_user&#39;<br/>- element “&lt;button title=&#34;Untrust Bank Account&#34; class=&#34;icon-button button-on&#34; icon=&#34;fa-solid fa-toggle-on fa-lg&#34; type=&#34;object&#34; name=&#34;action_untrust_bank_accounts&#34; invisible=&#34;not is_trusted_bank_account&#34;/&gt;” is shown in the view for groups: &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-16 17:30:00,522 43 WARNING 04464-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;field name=&#34;l10n_be_ambulatory_insurance_notes&#34;/&gt;</tt></b> are displayed, but they depend on the field <b><tt>l10n_be_has_ambulatory_insurance</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “l10n_be_has_ambulatory_insurance” is accessible for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39;<br/>- element “&lt;field name=&#34;l10n_be_ambulatory_insurance_notes&#34; string=&#34;Additional Information&#34; invisible=&#34;not l10n_be_has_ambulatory_insurance&#34;/&gt;” is shown in the view for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39; | &#39;dtg_hr_contract.group_hr_contract_user&#39;
2026-01-16 17:30:00,523 43 WARNING 04464-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;field name=&#34;l10n_be_hospital_insurance_notes&#34;/&gt;</tt></b> are displayed, but they depend on the field <b><tt>has_hospital_insurance</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “has_hospital_insurance” is accessible for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39;<br/>- element “&lt;field name=&#34;l10n_be_hospital_insurance_notes&#34; string=&#34;Additional Information&#34; invisible=&#34;not has_hospital_insurance&#34;/&gt;” is shown in the view for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39; | &#39;dtg_hr_contract.group_hr_contract_user&#39;