TIP: You can type at any time to perform a new search.
Purchase Order security
purchase_security · OCA/purchase-workflow
- Repository
- OCA/purchase-workflow · module folder · Try on Runboat
- Module version
- 1.0.0
- Category
- Purchase
- Folder size
- 0.1 MB
- License
- AGPL-3
- Application
- No
- Auto-installable
- No
- Website
- https://github.com/OCA/purchase-workflow
- Last tracking update
- 2026-08-13 11:29:18
- Authors
- Odoo Community Association (OCA), Tecnativa
- Maintainers
- Odoo Community Association (OCA), Tecnativa
- Committers
- Víctor Martínez, David Vidal, Weblate, OCA-git-bot, oca-ci
- Odoo dependencies
- Python dependencies
- None
- System dependencies
- None
- Required by
- None
- Description
This addon creates new groups in Purchase. Visibility of purchase orders is restricted for users in these groups. You can only see the purchase order: - User (own orders): If you are a follower of the partner or there is no user or you are the partner's user. - User (team orders): If you are a follower of the partner or there is no user or you are a user of your purchasing team.
Code Analysis ⓘ
Views touched (6)
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
purchase_order_form |
purchase.order.form (in purchase_security) | purchase.order | form | Inherits purchase.purchase_order_form |
purchase_team_form |
purchase.team.form | purchase.team | form | New |
purchase_team_tree |
purchase.team.form | purchase.team | list | New |
view_partner_property_form |
res.partner.property.form.inherit | res.partner | form | Inherits account.view_partner_property_form |
view_partner_tree |
res.partner.tree | res.partner | tree | Inherits base.view_partner_tree |
view_res_partner_filter |
res.partner.select | res.partner | Inherits base.view_res_partner_filter |
HTTP endpoints (0)
No HTTP endpoints found for this module.
Models touched (6)
New fields (0)
No new fields.
Public methods (0)No public methods.
New fields (0)
No new fields.
Public methods (0)No public methods.
New fields (2)
-
is_user_id_editableBooleancompute='_compute_is_user_id_editable' -
team_idMany2one → purchase.teambypass_search_access=Truecompute='_compute_team_id'index=Truereadonly=Falsestore=True args: 'purchase.team'
-
onchange_partner_id(self)@api.onchange('partner_id')
New fields (3)
-
nameCharrequired=True -
sequenceIntegerdefault=10 -
user_idsMany2many → res.userscolumn1='purchase_team_id'column2='res_users_id'comodel_name='res.users'relation='purchase_team_res_users_rel'string='Purchase Users'
-
open_form_view(self)Allow to open the form view from the editable tree view. The main reason to use the form view is to manage the team members of larger teams. The many2many_avatar_user widget in the tree view does not allow to remove some of the users if ellipsis ('+3') is triggered in the widget.
New fields (2)
-
purchase_team_idMany2one → purchase.teamcomodel_name='purchase.team'index=Truestring='Purchase team' -
purchase_user_idMany2one → res.userscomodel_name='res.users'domain="[('share', '=', False)]"index=Truestring='Purchase representative'
No public methods.
New fields (1)
-
purchase_team_idsMany2many → purchase.teamcheck_company=Truecolumn1='res_users_id'column2='purchase_team_id'comodel_name='purchase.team'copy=Falsereadonly=Truerelation='purchase_team_res_users_rel'string='Purchases Teams'
No public methods.
Loading…
Loading…
Loading…
Loading…
Loading…
Loading…
Loading…