Engineering · Published September 23, 2026
Permissions: From Roles to Data Scope
Most admin systems stop at menus and buttons. The hard part is showing each person only the data they should see.
Enterprise backends usually have three layers of permission: who can sign in, which menus they see and which buttons they can press. Once those exist, clients ask for a fourth: the same page should show different data to different people.
Three common data scopes
By organisation: a department manager sees their department, a regional manager their region, headquarters everything.
By ownership: sales see their own clients, leads see the team, administrators see all.
By classification: contracts and payroll are authorised individually, independent of role.
Two implementation notes
Do not scatter if-statements through business code. Extract the scope into a query condition builder and inject it centrally.
Permission changes need an audit trail: who changed whose access, and when. When something goes wrong, you can trace it.
Permission design is not about restricting people. It is about letting everyone work freely inside their responsibility, with out-of-scope actions blocked by default.
← Previous post
Mini Program or App? Start with Where the Business Happens
Next post →
Three Questions Worth Asking in User Interviews
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →