I worked with Firebase the last project I did, we had the same situation as yours, not specifically but similar, It was a hospital system, where each nurse have a user in the system, they can change things and update, add, remove, etc. but before anything there is the Supervisor he is one of the nurses but he has a higher level where all the request of modifying in the database goes to him and he should accept or decline them
however I don't remember we use the Firebase Authentication, cuz it would be hard doing it use it. I remember we build the whole thing from scratch.
I know this is stupid but we build the supervisor as nodes, where it has leaves, those leaves represent the nurses and one of them has the higher level, by doing this we give the higher nodes all the permissions and no one can access them only the Supervisor ( the responsible nurse )
What we did is converting the NoSql to SQL by building it on NoSql database ( if that make any sense ) lol, ik now you asking why working with NoSql and then build the Schema as SQL, simple we needed a Real-time Database, and Firebase was the best choice to start with
It was really challenging but in the end, we figured it out
Thanks for the response. I think you set me on the right track. Yeah looks like I won't be able to use firebase auth which was what I was trying to avoid but I don't really want to make it hard for children to create their own accounts, I'll have to create a user schema as you did, I guess the correct term is role based user permissions.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.