flâneur

A simple user permission model for sophisticated systems - DEV Community

dev.to · 3,800 words · saved by 1 readers

A space to discuss and keep up software development and manage your software career News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. An inclusive community for gaming enthusiasts A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here From composing and gigging to gear, hot music takes, and everything in between. Discussing AI software development, and showing off what we're building. Movie and TV enthusiasm, criticism and everything in-between. Memes and software development shitposting Web design, graphic design and everything in-between Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike A community of golfers and golfing enthusiasts For engineers building so

Introduction A friend asked me to detail the permission system that we have evolved over the years for use in some applications I maintain. These systems are ERP solutions wherein managers need to manage users' access to certain features and entities. These applications have been in continuous development for 15+ years and have implementations at some customers that have passed the 10 year mark. I think what we've arrived at is relatively easy for users to understand and manage and for programmers to utilize. The system could be utilized in any front-end language, but we store most of the busi

saved by

related reading