Role-Based Views for Leads vs New Hires

Published 2025-12-13 by Faraz Rahimi

The same app should not show a new hire the inventory adjustment hammer. Defaults are a safety system.

Role-Based Views for Leads vs New Hires

Tags: Auth, UX, React, Operations, unlisted

New hires get lookup, count, and exception create. Leads get override, mapping edits, and user unblock. I do this with roles from the database, not with a secret URL.

If a control is dangerous, it is not merely hidden in CSS. The API refuses it too.

Teach with the default, not a tour

A tour overlay will be skipped. A screen with one obvious job will be used. I add power later when they ask where it went, which is a good problem.

Temporary elevation

A lead standing next to a hire might need to approve one write. I prefer an approve button on the exception, not sharing the lead login.

Original post: https://farazrahimi.com/posts/role-based-views-for-leads-vs-new-hires