Portal Internal Log Notes
by Odoo DevHouse https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse$ 35.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 274 |
| Technical Name |
portal_log_note |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 274 |
| Technical Name |
portal_log_note |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse |
| Versions | 18.0 19.0 |
Portal Internal Log Notes
Empower authorized portal users to post private internal log notes from any portal record - helpdesk tickets, project tasks, sales orders, and more - without granting backend access. Notes are stored as standard Odoo Log Notes and are never visible to customers.
In standard Odoo, portal users can only post public chatter messages. There is no way for them to create internal log notes that are private to the internal team.
This creates real collaboration gaps in portal deployments:
- Portal employees cannot flag sensitive operational updates without sending a public message
- Internal teams miss private context from portal contributors
- Forcing portal users into the backend just to log a note is a security and UX risk
- Helpdesk technicians on portal cannot share troubleshooting notes away from the customer view
- No way to keep commercial or operational discussions private when collaborating via portal
- Customer sees all communication - no separation between internal and external messaging
- Backend access required for every internal note creates unnecessary access right sprawl
This module adds a "Log note" tab directly inside the portal chatter - right next to "Send message" - for users in the "Portal Internal Note Contributor" security group. When submitted, the note is stored as a standard Odoo Log Note: visible in the backend chatter to all internal users, completely hidden from customers, and never sent to portal contacts. No backend access is required. Works automatically on every portal-enabled record in Odoo.
- "Log note" Tab in Portal Chatter: Appears right next to "Send message" - identical to the backend experience, only for authorized users
- Security Group: "Portal Internal Note Contributor" - assign to portal users who need to post internal notes, all others remain unchanged
- Standard Log Note Storage: Notes are saved exactly like backend Log Notes - full author attribution, timestamp, and audit trail
- Customer Visibility Enforcement: Internal notes are automatically hidden from all portal customers - no extra configuration needed
- Author Attribution: Note is attributed to the portal user's name - the internal team sees exactly who posted it
- Cross-App Compatibility: Works automatically on every portal-enabled record - Helpdesk, Project, CRM, Sales, Purchase, and any custom model
- Internal Notifications: Triggers Odoo's standard internal follower notifications - no custom notification engine
- Server-Side Security: Group membership is validated on the server on every request - cannot be bypassed
- Backend Chatter Integration: Notes appear in the record's backend chatter with the standard Log Note styling
- No Core Modifications: Zero changes to Odoo core - fully upgrade-safe
- Mobile Responsive: Works on all screen sizes - phones, tablets, and desktops
- Multi-Company Support: Notes are scoped to the user's company context
1. Assign the Permission Group to a Portal User
Go to Settings -> Users & Companies -> Users, open the portal user, click the Groups smart button, and confirm "Portal Internal Note Contributor" is listed. All other portal users continue to work exactly as before.
2. Portal Page - "Send message" and "Log note" Tabs Appear in Chatter
The authorized portal user opens any portal record (here: Sales Order S00016). The Communication history chatter now shows two tabs: "Send message" for public messages and "Log note" for internal notes. Regular customers who are not in the group see only the standard "Send message" tab.
3. Click "Log note" - Standard Composer Opens
Clicking "Log note" activates it as the current tab and reveals the standard Odoo composer with a "Log" submit button - identical to the Log Note experience in the backend.
4. Write the Note and Click "Log"
The portal user types the internal note and clicks "Log" (or presses CTRL + Enter). The note is securely saved as a standard Log Note attributed to the portal user's name.
5. Customer View - Note is Completely Hidden
When the portal user (or any customer) views the same record's public chatter, the internal note is completely absent - the conversation shows as empty. Odoo's built-in internal note filtering handles this automatically with no extra setup.
6. Backend - Log Note Visible to the Internal Team
An internal user opens the same record in the Odoo backend. The note posted by Abigail Peterson (the portal user) appears in the chatter as a standard Log Note - with author name and timestamp - visible only to the internal team.
Installation & Configuration
- Install the Module: Install through Odoo Apps or copy to your addons path and update the app list
- Dependencies: Only requires the standard Messaging and Portal modules - included in every Odoo installation
- Restart & Update: Restart the Odoo server and update the module
- Assign the Group: Go to Settings -> Users, open the portal user, and add the "Portal Internal Note Contributor" permission group
- Verify on Portal: Log in as that portal user - the "Log note" tab now appears next to "Send message" in the chatter on every portal record
- No Further Config: Works automatically on all portal-enabled records - Helpdesk, Project, CRM, Sales, Purchase, and any custom model
Step 1: Assign the Permission Group
Go to Settings -> Users & Companies -> Users. Open the portal user's record. Add "Portal Internal Note Contributor" to their permission groups and save.
Step 2: Open a Portal Record
Log in as the portal user. Open any record that has a chatter - a Helpdesk Ticket, Project Task, Sale Order, Purchase Order, or any other portal-enabled record.
Step 3: Post the Internal Note
Scroll to the Communication history section. Click the "Log note" tab. Type your note and click "Log". The note is immediately visible to the internal team in the backend.
Step 4: Review Notes in the Backend
Log in as an internal user. Open the same record in the backend. The portal-created note appears in the chatter with the standard Log Note indicator, attributed to the portal user's name with a full timestamp.
Who Sees Internal Notes?
Internal Users - always see internal notes in the backend chatter.
Portal Note Contributors - can create notes from portal pages; the note is not shown back to them in the portal chatter.
Portal Customers - never see internal notes. This is enforced automatically by Odoo - no extra configuration needed.
Security
Permission is validated on the server on every submission - it cannot be bypassed through the browser, URL manipulation, or direct API calls. Only authenticated portal users who belong to the "Portal Internal Note Contributor" group can create internal notes.
Helpdesk Collaboration
Portal technician adds troubleshooting notes to a ticket without the customer seeing internal diagnostics or escalation discussions.
Project Task Updates
External contractor logs internal progress notes on assigned tasks - visible to the project team, hidden from the end client.
Sales Order Notes
Portal sales agent adds discount approval notes or supplier confirmation updates directly on the order without backend access.
Purchase Order Tracking
Procurement team members update supplier negotiation status and delivery risk notes on purchase orders from the portal.
CRM Lead Notes
Portal business development reps post qualification notes and competitive intelligence on CRM leads without requiring CRM backend rights.
Any Custom Portal Record
Any portal-enabled record in your Odoo instance automatically gains the internal note feature - no extra development needed.
Tighter Portal Collaboration
Bridge the communication gap between portal contributors and internal teams without compromising security.
Zero Backend Exposure
Portal users never need backend access to contribute internal context - least-privilege principle fully maintained.
Full Audit Trail
Every internal note is stored in Odoo's standard messaging system with author, timestamp, and record reference - complete traceability.
Customer Trust Protected
Sensitive operational discussions stay completely private. Customers only ever see messages explicitly intended for them.
Do You Need Assistance or Have a Feature Request?
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module