odoo-security

Configure and validate Odoo access control for models, records, and groups.

1|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-security-halim-23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odoo-security
Source: https://github.com/halim-23/odoo-dev-plugin/tree/main/skills/odoo-security
Command: npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-security-halim-23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Odoo security configuration for versions 17.0, 18.0, 19.0 (Community & Enterprise) requires careful setup of ACLs, record rules, groups, and field-level access, especially with multi-company environments. This skill provides guidance to implement and audit ir.model.access.csv entries, ir.rule records, and security groups, ensuring correct permissions across CE and EE.

Core Features & Use Cases

  • Configure and validate ACLs (ir.model.access.csv), record rules, groups, and field-level security for Odoo models.
  • Support multi-company setups and portal access considerations across v17/v18/v19 CE/EE.
  • Audit security configurations to ensure compliance and correct user permissions in both Community and Enterprise editions.

Quick Start

Configure and verify ACLs, rules, and group permissions for a new Odoo module across versions 17–19.

Frequently Asked Questions about odoo-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Odoo ACLs and record rules for a custom module?

To configure Odoo ACLs and record rules, define model access permissions in ir.model.access.csv and create ir.rule records for row-level security. Apply security groups and field-level access to enforce user permissions across Odoo modules.

How does multi-company security work in Odoo CE and EE?

Multi-company security in Odoo CE and EE uses record rules to restrict model access based on user company assignments. Proper group configurations and ir.rule records ensure users only view records within authorized companies.

Does this Odoo security setup support versions 17, 18, and 19?

Yes, this Odoo security setup supports versions 17.0, 18.0, and 19.0 across both Community and Enterprise editions. It validates ACLs, record rules, and group permissions for these specific Odoo platform versions.

What is the best way to audit field-level security in Odoo?

The best way to audit field-level security in Odoo is to review group permissions and validate ir.model.access.csv entries alongside ir.rule records. This ensures correct field access and compliance across Community and Enterprise environments.

Why are portal users seeing records they should not access in Odoo?

Portal users see unauthorized records when Odoo record rules or ACLs are misconfigured for their security groups. Check ir.rule records and portal access validations to ensure proper restrictions are applied to shared models.