The failure mode of role-based approval
Give twelve people the Manager role and any of the twelve can sign off anyone’s hours. When a client disputes an invoice or an auditor asks who approved a period, "a manager did" is not an answer. The approval exists but carries no information about accountability.
How reporting-line scoping works
Each membership stores a link to its manager. A reviewer may act on an entry only if the entry’s owner’s manager link points at that reviewer — or if the reviewer is an Admin or Owner. In Flocci Timesheets that check is applied on single, team-view and bulk endpoints alike.
Why the data layer, not the interface
A scope rule enforced only in the interface is bypassed by the first person who calls the API directly or uses a bulk action. Enforcing it in the data layer — including silently filtering unauthorised entries out of bulk operations rather than partially failing — means there is no path that widens scope.
What about matrix organisations
One reporting line per membership is a deliberate simplification: multiple approvers usually means nobody is accountable. Where reporting genuinely splits, model it as separate workspaces — one person can hold independent memberships with different roles, rates and managers, and switch between them.
