Hide admin menu if no admin option is available
If you have a menu “Admin tasks” and different admin tasks (like 10) that you could separately assign to each user, but there are users who don’t have any admin tasks, how would you deal with “Hiding admin menu” for those users?
How to define item level permissions in a relational database
I need to model a database design to provide item level permissions to users based on the user’s role access. I am using asp.net with sql server 2012
I am looking at similar experience on how SharePoint provides the security trimming when we access the resources with a SharePoint site (including search results)
How to define item level permissions in a relational database
I need to model a database design to provide item level permissions to users based on the user’s role access. I am using asp.net with sql server 2012
I am looking at similar experience on how SharePoint provides the security trimming when we access the resources with a SharePoint site (including search results)
How to define item level permissions in a relational database
I need to model a database design to provide item level permissions to users based on the user’s role access. I am using asp.net with sql server 2012
I am looking at similar experience on how SharePoint provides the security trimming when we access the resources with a SharePoint site (including search results)
Defining user operations on application/collection+json response?
I’m fairly new to Collection+JSON. I have a bunch of questions regarding Collection+JSON and user operations.
Designing a better performing total permissions setup for multiple permission levels
We’ve got a global system that we are attempting to solve a permissions issue around. Currently, our system serves a number of different applications out to our clients and each client has their own list of user types and users for our system. However, all of these things can be independent of each other. Such that Client A can have access to Application A and Application B. Client A might also have give different User Types, all with different Users. Each ‘level’ of usage would add a new level of complexity to how we give permissions out to everything.
Recommend an approach to decouple Product and Access code constructs, in order to simplify Product testing
I have some code that tightly couples Product specific code and Product-Access code. I am not sure how to untangle it. So for example, for testing Product, I have to mock up Access objects. And maybe there is no way around it, but maybe there is. I have code that goes something like this:
How to add permissions checks ‘after the fact’
I have a great number of PHP classes which perform the business logic of my application, e.g.
How to add permissions checks ‘after the fact’
I have a great number of PHP classes which perform the business logic of my application, e.g.
Design: How to handle user permissions across a system
My team is currently working on a massive refactor of a medium-sized application in PHP. We are doing our best to refactor our code on a module (Orders, Users, Products) basis. The issue that I am currently wondering about has to do with handling what a user is allowed to do on our system.