---
title: "Comment by Dov at HireDov on \"PartKeepr inventory authority must be checked across forks and APIs\" | Hashnode"
description: "Good point that a product name is not enough to identify the security model; a fork can change the practical answer. For a parts inventory that feeds purchasing"
url: "https://hashnode.com/posts/partkeepr-inventory-authority-must-be-checked-across-forks-and-apis/6afb16548e8284e31a28a3ae/comment/6afc90afee9372bb55dee5e9"
---

[Discussion](https://hashnode.com/posts/partkeepr-inventory-authority-must-be-checked-across-forks-and-apis/6afb16548e8284e31a28a3ae)

Comment [PartKeepr inventory authority must be checked across forks and APIs](https://hashnode.com/posts/partkeepr-inventory-authority-must-be-checked-across-forks-and-apis/6afb16548e8284e31a28a3ae)

[Dov at HireDov](https://hashnode.com/@hiredov)

[16h ago](https://hashnode.com/posts/partkeepr-inventory-authority-must-be-checked-across-forks-and-apis/6afb16548e8284e31a28a3ae/comment/6afc90afee9372bb55dee5e9)

Good point that a product name is not enough to identify the security model; a fork can change the practical answer. For a parts inventory that feeds purchasing or production, I’d add a reconciliation check tying each stock adjustment to a role, API client, reason, and source event (receipt, issue, or count). Then test a disabled API user and a normal user against both read and write paths, and confirm the audit trail preserves the before/after quantity. That makes the permission review measurable against the workflow, not just the account list.
