القائمة
Manage access rights, user groups, record rules, and field-level security. Use for permissions, security, access control, roles, groups, or "who can see/edit what".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Remove signs of AI-generated writing from text. Use when drafting or editing user-facing copy in Odoo (emails, product descriptions, website pages, knowledge articles, chatter messages) so it reads natural and human-written. Based on Wikipedia's "Signs of AI writing" guide.
Post messages and notes in Odoo chatter, schedule activities, attach files, and manage followers via the external API. Use when the user wants to log a call, leave an internal note, send an email through Odoo, schedule a follow-up, or add an attachment to any record.
Build automated actions, server actions, scheduled jobs, and email triggers in Odoo. Use when the user wants "when X happens, do Y", or a scheduled/recurring task.
Work with vendors, RFQs, purchase orders, receiving goods, and paying vendor bills. Use when the user mentions buying, purchase, inkoop, vendors/suppliers, POs, bills, or procurement.
Deduplicate, enrich, and fix data quality — especially contacts, products, leads. Use for dedupe, merging duplicates, fixing formatting, enrichment, or data-quality audits.
Add custom fields, adjust views/forms, and customize models without writing a module (Studio-style changes). Use when the user wants to add a field, change a form layout, or customize a view.
| name | permissions |
| description | Manage access rights, user groups, record rules, and field-level security. Use for permissions, security, access control, roles, groups, or "who can see/edit what". |
| triggers | ["permissions","security","access","rights","roles","groups","rechten","rollen","groep","record rule"] |
Who can do what, on which records, and which fields.
res.users — user accountres.groups — group (a role, e.g. "Sales / User")ir.model.access — CRUD access per group × model (read/write/create/unlink)ir.rule — record rule: domain filter per group, restricts which rows they seeir.model.fields — groups field for field-level visibilityir.model.access) — can this group touch this model at all?ir.rule) — which rows within that model? (applied as AND for non-global rules)groups_id = [(4, group_id)] on res.usersres.groups, add implied_ids for inheritance (e.g. Manager implies User)ir.rule with domain [('user_id', '=', user.id)] limits to "own records"groups on ir.model.fields to restrict visibilityimplied_ids)sudo() in server actions bypasses all rules — use sparingly, never in user-facing code paths.ir.rule with global = True applies to everyone regardless of groups — rare, use with care.implied_ids — user in "Sales Manager" automatically also has "Sales User".company_ids on user) are a separate layer — multi-company needs extra care.