| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 3131 |
| Technical Name |
odaura_ai |
| License | OPL-1 |
| Website | https://odaura.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 3131 |
| Technical Name |
odaura_ai |
| License | OPL-1 |
| Website | https://odaura.com |
AI Suite for Odoo
Multi-provider AI chat with governed access to your live Odoo data. Analyze records, detect patterns, generate forecasts, and share insights — all without leaving your ERP.
Odoo 19 Compatible ACL-Enforced Access Data Never Trained On On-Premise & Ollama 5 AI BackendsIntelligent analysis built for the Odoo
AI Suite for Odoo puts a governed, multi-provider AI assistant directly inside your ERP. Business users, analysts, and managers can query live operational data, detect patterns, and generate forecasts — all without leaving Odoo and without exporting sensitive data to external tools.
Every query is routed through Odoo’s ORM layer. Record rules, field-level restrictions, and access groups are enforced before any data reaches the AI backend. The AI can read records, but it can never create, update, or delete anything.
Everything your teams need from AI
A complete AI capability set, fully governed by your existing Odoo security configuration.
Private AI Chat Per User
Fully isolated per-user chat sessions. No shared state, no cross-user visibility. Each session is private to the authenticated individual.
ACL-Enforced Data Access
All queries run through Odoo’s ORM. Record rules, access groups, and field-level restrictions apply before any data reaches the AI model.
Forecasting & Pattern Detection
Request forward-looking projections and trend analysis from historical Odoo data. Seasonal patterns, anomalies, and pipeline health in plain language.
AI-Generated Chart Images
Bar charts, line graphs, pie charts delivered as image files inside the chat. Requires an OpenAI model (DALL-E 3, DALL-E 2, or GPT-Image-1).
5 AI Providers
OpenAI, Anthropic, Google Gemini, Mistral, and Ollama. Ollama runs entirely on your infrastructure — no external calls, full data residency.
Role-Based Access Control
Define which roles access which AI backends and Odoo data domains using native Odoo access groups. No custom permission system needed.
Agentic Tool-Use Loop
Up to 8 sequential tool calls per response — search, read, and traverse Odoo records to answer complex multi-step queries automatically.
Share to Discuss & Email
Forward any AI response or chart image to Odoo Discuss channels, group chats, or DMs. Or open the Send by Email window pre-filled with the AI content.
Read-Only AI Access
The AI can search and read records but cannot create, update, or delete anything. This is a hard boundary at the tool layer, not a configuration option.
See it in action
Real screens from the running module.
A private workspace for every user
Each Odoo user gets a dedicated, isolated AI chat session. Conversations are not visible to other users or administrators unless audit access is explicitly configured. There is no shared session state.
The interface is embedded directly inside Odoo — no browser extensions, external tools, or data exports required.
Business insights from live Odoo data
The AI has direct, permission-filtered access to your Odoo models. Ask questions in natural language and receive structured summaries, exception highlights, and contextual analysis from live records.
Share AI insights without leaving Odoo
Forward any AI response or chart image directly to Odoo Discuss. Choose a department channel, a group conversation, or a direct message. To loop in an external party, click Send by Email — the compose window opens pre-filled with the AI content.
Enterprise governance, not an afterthought
AI access is governed by the same rules that govern any other data access in your Odoo instance.
ORM-Level Access Enforcement
All AI queries execute through the authenticated user’s ORM context. Record rules, ACLs, and domain filters apply exactly as for any standard Odoo operation.
Pre-Query Data Filtering
Restricted fields, confidential records, and out-of-scope models are excluded before data is sent to the AI backend. The AI receives only what the user is authorized to view.
Session Isolation
Chat sessions are bound to a single authenticated user. No shared session state. Conversation history is private and not visible to colleagues or admins by default.
Read-Only Tool Boundary
All three AI tools (search, read record, get fields) are strictly read-only. The AI cannot create, update, or delete any Odoo record. This is enforced at the tool layer — not a setting.
Configurable Data Scope
Define exactly which Odoo models and fields are in scope per role. Sales data in, HR/payroll data out. Restrictions are enforced at the retrieval layer, not just the UI.
Conversational Audit Trail
All messages are persisted in the database per user session. Every query and AI response is traceable. Sessions are independently reviewable by authorized administrators.
Up and running in four steps
No structural changes to your database or security configuration required.
Enable AI Backends
Configure one or more AI providers in the module settings. Assign each backend to specific user groups or make it globally available.
Assign Permissions
Use Odoo’s standard access group management to define who can use AI features and which backends are available to each role.
Configure Data Scope
Define which Odoo models and fields are in scope per role. Models not explicitly permitted are excluded from AI access entirely.
Define AI Resources
Create AI resource records specifying backend parameters and dataset restrictions tailored to a department or use case.
Built on Odoo’s native infrastructure
Security, data access, and UI rendering all use established Odoo framework patterns — no external dependencies or custom security layers.
| Odoo Compatibility | Odoo 19.0 â follows updated view syntax, OWL 2 component patterns, and current controller conventions. |
| Security | ORM, record rules, and ACLs. No bypass of standard permission infrastructure. Multi-company rules and ownership restrictions are honored. |
| AI Backends | OpenAI, Anthropic, Google Gemini, Mistral, Ollama. Modular architecture â backends can be swapped or extended without UI changes. |
| Image Generation | OpenAI only: DALL-E 3, DALL-E 2, GPT-Image-1. Not supported on Anthropic, Gemini, Mistral, or Ollama. |
| AI Tools | search_odoo, read_odoo_record, get_odoo_fields â all strictly read-only. No write, create, or delete operations exist at the tool layer. |
| Frontend | OWL 2. Reactive state, Odoo service registry for dialogs, RPC, and notifications. No external JS libraries. |
| Deployment | On-premise, Odoo.sh, private cloud. No SaaS dependency. Ollama support enables fully air-gapped, offline deployments. |
© 2025 Odaura. All rights reserved. Not affiliated with Odoo S.A.
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