A common failure mode: one generic interface handed to everyone in the company. The commercial team sees stock they're not allowed to edit; the warehouse team wades through a quote list they'll never touch. Everyone does their job slower.
The one-size-fits-all interface is the default because it's cheaper to build. One set of screens, one set of components, one set of API calls. But the cost of that generic interface is paid by every user, every day, in extra clicks, irrelevant information, and cognitive load. The commercial person who has to mentally filter out inventory fields from every screen. The warehouse worker who scrolls past quote-creation buttons they'll never click. The tiny daily frictions that add up to a tool people tolerate rather than reach for.
Permissions as UX Quotery uses permissions not just to block actions but to shape the interface. Commercial users don't see the stock adjustment button; warehouse users don't see the quote cancel action. The platform reads the user's groups and renders accordingly.
This is the difference between authorization as a gate and authorization as a design principle. A gate says 'you can't do this' after you try. A design principle says 'you won't even see this unless it's relevant to you.' The latter is faster, quieter, and more respectful of the user's time. It also reduces support burden — users can't ask about features they can't see, and they can't accidentally stumble into workflows they're not authorized to complete.
Same API, different defaults Under the hood every request hits the same API. The difference is the default filters and the default screens. A commercial user's quote list is scoped to their own quotes; a manager's is tenant-wide. Same endpoint, different defaults.
This uniformity underneath is what makes the role-specific UX sustainable. There's one API to maintain, one set of business rules to enforce, one source of truth. The frontend layers role-specific defaults on top — filter presets, default sort orders, visible columns — but the API contract is identical. When a commercial person and a manager look at the same quote, they see the same data. The only difference is what else they see around it.
Fewer decisions, faster days The tool's job is to make the next action obvious. Every screen in Quotery has a primary CTA tuned to the user's role — close this quote, post this delivery, approve this return. Less choice, less fatigue.
Decision fatigue is real in operations software. When every screen presents 15 possible actions, the user spends mental energy on 'what should I do next?' instead of 'how do I do the thing I know needs doing?' By surfacing exactly one primary action per screen — the one that 80% of users need 80% of the time — the tool reduces the cognitive cost of every interaction. Secondary actions are still available, but they're visually subordinate. The design says 'this is probably what you want,' and most of the time, it's right.