Hide Product Vendors by Role and User -- Enforced Everywhere
Keep supplier identities, purchase prices, and lead times confidential from sales, warehouse, and portal users -- with pre-built role profiles, per-user exceptions, and a full access audit log.
Every product's Purchase tab shows the full vendor list -- supplier names, negotiated prices, and lead times -- to anyone who can open the form, a list view, an export, or the API. Sales reps, warehouse staff, and portal customers routinely see sourcing data they should never have, and a global on/off toggle cannot tell a trusted buyer apart from everyone else.
A single record rule blocks vendor data everywhere -- form, list, export, portal, and API -- for every unauthorised user, while pre-built role profiles, per-user overrides, and an audit log give administrators no-code control over exactly who sees what.
Everything you need to control vendor visibility
Every capability below is implemented in the module.
Enforced Everywhere, Not Just the Form
A global record rule blocks vendor data in the product form, list views, exports, the portal, and the API alike -- not merely hidden on one screen.
No-Code Visibility Profiles
Pre-built profiles map a role -- Sales, Purchasing, Inventory, Administrators -- to sees-vendors yes/no, applied in one click with no record-rule authoring.
Per-User Exceptions
Grant or revoke a single trusted -- or untrusted -- user's access with Inherit / Always show / Always hide, without touching their role's group settings.
One Central Control Panel
Profiles, User Visibility, and the Access Log live under a single Vendor Visibility menu -- no settings scattered across unrelated screens.
Who-Sees-What Preview
The Profiles list shows, at a glance, which roles currently see vendor data and which do not -- so admins verify the outcome before it ships.
Full Vendor Access Audit Log
Every genuine read of vendor data is logged with user, product, and timestamp -- giving compliance-minded buyers a traceable record.
Portal and Website Safe by Default
The same record rule that protects the backend blocks portal and website users too, so supplier data never leaks to a public or customer-facing catalog.
Purchasing Workflows Keep Working
The rule restricts reads only, so confirming a purchase order can still create or update vendor pricing even for a user who cannot see it.
How it works
Install & Review Defaults
Administrators and Purchasing Managers keep seeing vendor data by default; everyone else does not -- no configuration required on day one.
Apply a Role Profile
Open Vendor Visibility > Profiles, toggle Sees Vendor Data for a role, and click Apply -- no record rules to write by hand.
Grant or Revoke Per User
Set a single user's Vendor Data Visibility to Always Show or Always Hide to override their role for that one person.
Review the Audit Log
Check Vendor Visibility > Access Log to see who viewed vendor data, on which product, and when.
See it in action
A look at the visibility profiles, per-user overrides, and audit log that keep vendor data confidential.
The Visibility Profiles list maps each role to a sees-vendors yes/no flag, with success and warning row colours showing whether a profile is currently applied, plus an Apply All button for bulk changes.
A profile's form shows the linked role, its user count, the Sees Vendor Data toggle, and a one-click Apply button -- no record-rule authoring required.
The User Visibility list shows every user's override alongside the computed Can See Vendors flag, so an administrator can audit the whole team at a glance.
On the user form, Vendor Data Visibility can be set to Inherit, Always Show, or Always Hide -- a per-user exception that overrides the role default.
The read-only Access Log records every user who viewed vendor data, on which product, and when -- with a Today filter and group-by user or product.
For an authorised user, the product's Purchase tab still shows the full vendor list with prices and lead times; unauthorised users see nothing -- the same field, enforced by the record rule.
Frequently asked
Does this only hide vendors on the product form, like other apps?
No. A global record rule blocks read access to vendor data everywhere -- the product form, list views, exports, the portal, and the API -- for anyone not authorised. Many competing apps only hide the field on one view, leaving the data reachable through an export or the API.
Can I grant one trusted user access without changing their whole team's role?
Yes. Every user has a Vendor Data Visibility field (Inherit, Always Show, Always Hide) that overrides whatever their role or profile would otherwise grant -- a per-user exception with no group editing required.
What do portal and website customers see?
By default, portal users have no profile granting vendor visibility, so the same record rule that protects the backend blocks them too -- supplier identities and prices never reach the storefront.
Does blocking vendor reads interfere with purchasing workflows, like confirming a purchase order?
No. The record rule restricts read access only -- creating or updating vendor pricing (for example when a purchase order confirmation stamps a new price) is never blocked, even for a user who cannot see the data.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Hide product vendor lists, prices, and lead times from unauthorised users with role profiles, per-user overrides, and a full audit trail -- enforced everywhere, not just the product form.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 343 |
| Technical Name |
cerevantix_hide_vendors_of_product |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module