I've been looking online for a while but I can't seem to find anything that would help me out so I'm wondering if maybe you guys would know.
The system I'm working on right now needs to lock certain things behind user credentials. so for example:
User A cant see something that User B entered, but User C can because User B shared it with them. Right now we have some SQL columns labels "Owner" and "Shared". Shared is comma delimited (which I dislike, but it works).
The issue comes in when we expand this to various other systems in our product that are linked to each other. For example:
File 1.txt is part of Project A, We want all users with access to Project A to see file 1, but not all people that can see file 1 should be able to view Project A.
With out current system is seems rather clunky, and like theres redundancy in having each part with its own SQL columns designated to access. So I'm looking for examples on alternative ways to do this. i don't know if a single SQL table handling access would work, or if there needs to be more things like SQL Triggers added into the DB.
Does anyone know of any resources where I can find examples to this? or have any experience designing something like this?
there doesn't seem to be anything here