AI Agent Approvals
by Odoo Apps by Mithahara https://apps.odoo.com/apps/modules/browse?author=Mithahara$ 298.99

AI Agent Approvals
Hold an AI agent's writes to the models you choose until a person approves them, with the old and new values side by side
An agent that can write to your database will eventually write something you would not have agreed to. Rate limits and logs help afterwards. For the handful of models where a wrong write is expensive to undo - prices, customers, posted documents - what you want is a person in front of it.
Name those models on the agent. Its changes to them stop being applied and start being requests.
What is there now, what the agent wants to put there, and two buttons.
Approve applies exactly what was asked
The values are kept verbatim as the agent sent them, so what is applied is what was reviewed - not something rebuilt afterwards from a description of it.
It survives its own refusal
Holding a change means refusing it, and Odoo rolls a request back when an error reaches it - which would discard the record remembering what the agent asked. The request is written on its own database cursor, so the agent is told no and the queue still has the change.
Records that moved on are refused
If somebody changed the records after the agent asked, the old values on screen are no longer what is there. Approving is refused rather than overwriting whoever got there first on a decision taken about different data.
A batch is one decision
The agent asked once. Splitting a batch would let half be approved and half refused - a state nobody asked for and no agent knows how to recover from.
Only where you asked for it
Everything outside the named models carries on at machine speed. The point is not to slow the agent down everywhere - an approval queue nobody can keep up with gets approved without reading, which is worse than none.
Requirements, and what this is not
Odoo 19 Community or Enterprise. Requires AI Agent Guardrails, which registers which logins are agents. It does not decide for you and does not restrict what the agent may read. The approval records themselves are never held - holding a change to them would need approving, and nobody could approve the first one.
Screenshot
Support
Questions before or after purchase: support@mithahara.com.
Need this tailored to your business?
This app covers the common case out of the box. If you need it adapted to a specific workflow, integrated with another system, or extended with a feature you don't see here, we do custom Odoo development too - reach out at support@mithahara.com and we'll scope it.
More apps by Mithahara
A write ceiling and change log for MCP agents.
Every key, and when it was last used.
Hide or lock a field for the groups you choose.
What one user can do on one model. Free.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Community Apps Dependencies | Show |
| Lines of code | 700 |
| Technical Name |
mh_ai_agent_approvals |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules/browse?author=Mithahara |
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