odoo-security
Skill2 starsChanged 3 months agoMITView on GitHub
Functional expertise in Odoo's security and permission architecture, covering Users, Groups, Access Rights, and Record Rules.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- odoo/odootheir own version, first seen Oct 8, 2026
- echozen88/odoo-claude-codetheir own version, first seen Feb 4, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- odoo/odoo★ 56ksame name
- echozen88/odoo-claude-code★ 7same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- odoo-attendanceSkill
- odoo-crmSkill
- odoo-dashboardsSkill
- odoo-data-opsSkill
- odoo-devSkill
- odoo-documentsSkill
- odoo-field-serviceSkill
- odoo-financeSkill
- odoo-frontdeskSkill
- odoo-get-startedSkill
- odoo-helpdeskSkill
- odoo-hrSkill
- odoo-introspectorSkill
- odoo-inventorySkill
- odoo-knowledgeSkill
- odoo-mrpSkill
- odoo-plmSkill
- odoo-productsSkill
- odoo-projectsSkill
- odoo-purchasingSkill
- odoo-qualitySkill
- odoo-relationsSkill
- odoo-reportsSkill
- odoo-salesSkill
- odoo-spreadsheetsSkill
- odoo-uxSkill
- odoo-websiteSkill
- odoo-worksheetsSkill
- odoo-workspaceSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Mandate: When creating or updating records, ensure the company_id is set correctly.
- Distinctive: line 29
When a user encounters an "Access Error":
- Very specific: line 30
Groups: Verify the user's assigned groups in res.users.
- Very specific: line 31
Access Rights: Check ir.model.access for the target model and the user's groups.
- Very specific: line 32
Record Rules: Check ir.rule for active domains on the target model.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Odoo Security & Access Control
This skill provides the agent with high-level functional expertise in Odoo's security and permission architecture, covering Users, Groups, Access Rights, and Record Rules.
Core Mandates
1. The Security Hierarchy
Understand how Odoo grants permissions:
- Users (
res.users): Individual accounts. - Groups (
res.groups): Logical roles (e.g., "Sales / User", "Accounting / Manager"). - Access Rights (
ir.model.access): Model-level permissions (Can I Read/Write/Create/Delete ANY record in this model?). - Record Rules (
ir.rule): Row-level permissions (Can I see THIS specific record?). Enforced viadomain_forcefilters.
2. Record Rule Enforcement
- Mandate: Record rules strictly filter data at the database level. Even if a user has "Read" access on a model via Access Rights, a Record Rule can hide specific records.
- Evaluation: Odoo applies Record Rules using specific logic:
- Global Rules: (no group assigned) are applied using AND (all must pass).
- Group Rules: (assigned to a group) are applied using OR among rules of the same group.
3. Multi-Company Security
- Strict Isolation: Odoo uses Record Rules to enforce multi-company isolation.
- Mandate: When creating or updating records, ensure the
company_idis set correctly. Attempting to link records from different companies (e.g., a Sales Order in Company A pointing to a Warehouse in Company B) will trigger a "Multi-company Access Error".
4. Troubleshooting Workflow
When a user encounters an "Access Error":
- Groups: Verify the user's assigned groups in
res.users. - Access Rights: Check
ir.model.accessfor the target model and the user's groups. - Record Rules: Check
ir.rulefor active domains on the target model. Analyze thedomain_forceto see if it's filtering out the specific record ID.
Available Resources
security-logic.md: Deep-dive into Access Rights vs. Record Rules, Evaluation Logic, and Multi-company rules.security-fields.json: Technical map for Users, Groups, Access, and Rule models.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.