fix: allow groomer role to access invoices endpoint #340
Reference in New Issue
Block a user
Delete Branch "fix/gro-805-invoices-rbac"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
groomerrole alongsidemanagerto access/api/invoices/*routeTest plan
cc @cpfarhood
Deployed to groombook-dev
Images:
pr-340URL: https://dev.groombook.farh.net
Ready for UAT validation.
QA Review: APPROVED
CI: All green — Build, Lint & Typecheck, Test, E2E Tests, Web E2E (Dev), Deploy PR to groombook-dev all pass.
Code: Single-line change — on route. Correctly extends invoice access to groomer role without affecting existing manager permissions.
Ready for CTO technical review.
cc @cpfarhood
QA Review: APPROVED
CI: All green — Build, Lint & Typecheck, Test, E2E Tests, Web E2E (Dev), Deploy PR to groombook-dev all pass.
Code: Single-line change —
requireRole("manager", "groomer")on/invoices/*route. Correctly extends invoice access to groomer role without affecting existing manager permissions.Ready for CTO technical review.
cc @cpfarhood
Ready for QA Review
This PR is complete and ready for your review.
Summary
requireRole("manager")→requireRole("manager", "groomer")on the/invoices/*routeAcceptance Criteria
requireRolecall on/invoices/*includes"groomer"alongside"manager"— diff confirmeddevbranchfix: allow groomer role to access invoices endpointPlease review and approve so this can move to CTO.
cc @cpfarhood
CTO approved. Single-line RBAC fix is correct —
requireRoleaccepts variadicStaffRole[]args,groomeris a valid role in the union type. No privilege escalation risk; groomers legitimately need invoice access for their appointments. Consistent with adjacent route guards. CI all green. cc @cpfarhoodEngineer approval. RBAC fix correctly grants groomer role access to invoices endpoint. CI all green. cc @cpfarhood