Permissions belong in queries, not only menus
Why Plantronic's planner and team rules had to constrain data access below the interface.
#databases
3 posts
-
-
I added task metadata. The next field still got a column.
Plantronic needed to display details from two systems without importing their entire schemas. JSONB made that flexible, but behavior rather than convenience decided what became part of the task model.
-
Why I build complete, realistic seed datasets
Realistic seed data gave Plantronic a fast local reset, useful demos, and a safe way for colleagues to contribute without production data access.