Partner category security (crm extension)
This is a glue module between "partner_category_security" and "crm" to mitigate the permissions to manage contact tags.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0This glue module limits what salespeople can do with contact tags in the CRM app, giving them read-only access instead of full management rights.
This module connects two existing features: the contact tag security rules and the CRM app. Its only visible effect is a change in permissions.
- Salespeople (the standard sales team user group) can still see contact tags, but they can no longer create, edit or delete them from the CRM screens.
- The restriction is applied to the contact tag model (
res.partner.category), which is the same list of tags used on contacts and leads/opportunities. - No new menus, buttons, reports, checks, computed fields or scheduled actions are added by this module.
- It installs automatically when both the contact tag security module and CRM are present, so no manual setup is needed.
In practice, a salesperson working in CRM can still assign existing tags to contacts or opportunities, but managing the tag list itself is reserved for users with the appropriate rights. This keeps the tag catalogue consistent and avoids duplicates created by sales users.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/partner-contact.
terminal Installation and usage
OCA documentation · Odoo 16.0Usage
Source · Odoo 16.0- Sales / User: Own Documents Only permission only allows reading the tags assigned to contacts.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.